Stages Documentation

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
75:process_feedback_jira [2020/04/09 09:40] – fnpk75:process_feedback_jira [2021/05/12 16:50] – old revision restored (2020/07/13 11:08) fnpk
Line 32: Line 32:
       <!-- 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  -->
  
-      <!-- +      <!--  
-      The user will be asked to enter the following text fields. All text fields are optional. +      See common feedback documentation
-      - 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 id of the custom field in Jira (e.g. "customfield_10101").       - The "target" defines the id of the custom field in Jira (e.g. "customfield_10101").
       - Optional: The targetType defines the type of the Jira field. Supported Jira fields see below.       - Optional: The targetType defines the type of the Jira field. Supported Jira fields see below.
Line 41: Line 39:
       <attributes>       <attributes>
         <attribute ident="description" type="text" target="description" />         <attribute ident="description" type="text" target="description" />
-        <!-- 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="priority" type="string" target="customfield_10101" /> 
-        <attribute ident="component" type="string" target="components" targetType="components" /> 
-        --> 
       </attributes>       </attributes>
  
       <!--       <!--
-      You can map element specify information to your Jira issue. These sources are available: +      See common feedback documentation
-      - 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 id for the custom field in Jira (e.g. "customfield_10101").       The "target" defines the id for the custom field in Jira (e.g. "customfield_10101").
       Optional: The targetType defines the type of the Jira field. Supported Jira fields see below.       Optional: The targetType defines the type of the Jira field. Supported Jira fields see below.
Line 66: Line 53:
         <attribute source="creatorUsername" target="customfield_10108" />         <attribute source="creatorUsername" target="customfield_10108" />
       </system-attribute-mappings>       </system-attribute-mappings>
 +
 +      <!--
 +      See common feedback documentation
 +      The "target" defines the id for the custom field in Jira (e.g. "customfield_10101").
 +      Optional: The targetType defines the type of the Jira field. Supported Jira fields see below.
 +      -->
 +      <custom-attribute-mappings>
 +        <attribute value="Stages" target="customfield_10200" />
 +      </custom-attribute-mappings>
     </host>     </host>
   </feedback-system>   </feedback-system>