This is an old revision of the document!


Process Feedback PTC-ILM specific

First of all, create or choose a ILM item type where the feedback will be collected.

Stages will use the SOAP interface to create the items.

Stages config.xml

To enable the following configuration section must be added in the conf/config.xml:

<?xml version="1.0" encoding="UTF-8" ?>
<stages-config>
  <!-- Insert this block to your stages config.xml file -->
  <feedback-system name="ptcilm">
 
    <host url="http://integrity.example.com:7001/webservices/10/2/Integrity/?wsdl">
 
      <!-- Credentials for a (technical) user who is allowed to create issues -->
      <property name="user" value="user" />
      <property name="password" value="secret" />
 
      <!-- Define the item type where the issue should be created in -->
      <property name="type" value="feedback" />
 
      <!-- As alternative to the project key you can specify the project by its id -->
      <property name="imweb" value="http://integrity.example.com:7001/im" /> -->
 
 
      <!-- The summary field will always be available and is automatically mapped to the Jira "Summary" field  -->
 
      <!--
      The user will be asked to enter the following text fields. All text fields are optional.
      - The "ident" must be unique and is used to identify the right translation property.
      - The "type" defines if the field is a multi-line text ("text") or a single line string ("string").
      - The "target" defines the name of the field in ILM (e.g. "Impact").
      - Optional: The targetType defines the type of the field. Supported PTC-ILM fields see below.
      -->
      <attributes>
        <attribute ident="description" type="text" target="Description" targetType="longtext" />
        <!-- The following fields could be enabled if you want the users to provide more data with every feedback item: -->
        <!--
        <attribute ident="impact" type="string" target="Impact" />
        -->
      </attributes>
 
      <!--
      You can map element specify information to your ILM item. These sources are available:
      - elementUrl e.g. https://stages.example.com/stages/index.html#/workspace/200/_vv/(process/activity/_wUV9sBbNHr-aicWx33VsQA)
      - workspaceName e.g. "Software Engineering"
      - workspacePath e.g. "Company | Software"
      - creatorFullname "John Doe"
      - creatorUsername "jdoe"
      The "target" defines the name for the field in ILM (e.g. "customfield_10101").
      Optional: The targetType defines the type of the ILM field. Supported fields see below.
      -->
      <system-attribute-mappings>
        <attribute source="elementUrl" target="Element Url" />
        <attribute source="workspaceName" target="Workspace Name" />
        <attribute source="workspacePath" target="Workspace Path" />
        <attribute source="creatorFullname" target="Creator Fullname" />
        <attribute source="creatorUsername" target="Assigned User" targetType="user"/>
      </system-attribute-mappings>
    </host>
  </feedback-system>
</stages-config>

Supported Jira fields

  • shorttext: targetType=“” (Empty)
  • longtext: targetType=“longtext” (Also with rich text setting)
  • user: targetType=“user”

Be aware: If you choose user then the user entered values or the Stages username must match / exist in ILM. Otherwise the item creation will fail.

Other ILM fields are not supported at the moment.