Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revisionBoth sides next revision
75:process_feedback_ptcilm [2020/01/23 16:46] – created fnpk75:process_feedback_ptcilm [2020/01/27 08:46] – fnpk
Line 1: Line 1:
 ====== Process Feedback PTC-ILM specific ====== ====== Process Feedback PTC-ILM specific ======
  
-First of all, create or choose a PTC item type where the feedback will be collected.+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 will use the SOAP interface to create the items.
- 
-TODO!!! 
  
 ===== Stages config.xml ===== ===== Stages config.xml =====
Line 15: Line 13:
   <!-- Insert this block to your stages config.xml file -->   <!-- Insert this block to your stages config.xml file -->
   <feedback-system name="ptcilm">   <feedback-system name="ptcilm">
-   
-  http://integrity10.er.methodpark.de:7001/webservices/10/2/Integrity/?wsdl 
-    <host url="https://jira.example.com/jira"> 
  
-      <!-- Credentials for a (technical) user who is allowed to create issues in the Jira project --> +    <host url="http://integrity.example.com:7001/webservices/10/2/Integrity/?wsdl"> 
-      <property name="authentication.type" value="basic" />+ 
 +      <!-- Credentials for a (technical) user who is allowed to create issues -->
       <property name="user" value="user" />       <property name="user" value="user" />
       <property name="password" value="secret" />       <property name="password" value="secret" />
  
-      <!-- Define the project where the issue should be created in --> +      <!-- Define the item type where the issue should be created in --> 
-      <property name="projectKey" value="FEED" />+      <property name="type" value="feedback" /> 
       <!-- As alternative to the project key you can specify the project by its id -->       <!-- As alternative to the project key you can specify the project by its id -->
-      <!-- <property name="projectId" value="1234" /> -->+      <property name="imweb" value="http://integrity.example.com:7001/im" /> -->
  
-      <!-- Define the name of the issue type that should be created --> 
-      <property name="issuetypeName" value="Task" /> 
  
-      <!-- The summary field will always be available and is automatically mapped to the Jira "summary" field  -->+      <!-- The summary field will always be available and is automatically mapped to the Jira "Summary" field  -->
  
       <!--       <!--
Line 38: Line 33:
       - The "ident" must be unique and is used to identify the right translation property.       - 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 "type" defines if the field is a multi-line text ("text") or a single line string ("string").
-      - The "target" defines the id of the custom field in Jira (e.g. "customfield_10101"). +      - The "target" defines the name of the field in ILM (e.g. "Impact"). 
-      - Optional: The targetType defines the type of the Jira field. Supported Jira fields see below.+      - Optional: The targetType defines the type of the field. Supported PTC-ILM fields see below.
       -->       -->
       <attributes>       <attributes>
-        <attribute ident="description" type="text" target="description" />+        <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: -->         <!-- The following fields could be enabled if you want the users to provide more data with every feedback item: -->
         <!--         <!--
-        <attribute ident="annual_savings" type="string" target="customfield_10100" /> +        <attribute ident="impact" type="string" target="Impact" />
-        <attribute ident="priority" type="string" target="customfield_10101" /> +
-        <attribute ident="component" type="string" target="components" targetType="components" />+
         -->         -->
       </attributes>       </attributes>