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
Last revisionBoth sides next revision
72:jira_feedback [2019/01/29 14:16] – Fixt syntax highlighting fnpk72:jira_feedback [2019/06/03 19:46] – emr
Line 11: Line 11:
  
 To configure Stages, ids of the Jira custom fields are required. There are several ways to find them out in the [[https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html|Jira documentation]]. The ids consist of the prefix ''customfield_'' and a number e.g. ''customfield_10101''. To configure Stages, ids of the Jira custom fields are required. There are several ways to find them out in the [[https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html|Jira documentation]]. The ids consist of the prefix ''customfield_'' and a number e.g. ''customfield_10101''.
 +
 +Stages will use the Jira REST interface to create the issue. [[https://docs.atlassian.com/software/jira/docs/api/REST/8.2.1/?_ga=2.49222754.599077736.1559584770-75849189.1559330334#api/2/issue-createIssue|See here]] for more info.
 +
 ==== Stages config.xml ==== ==== Stages config.xml ====
  
 To enable the following configuration section must be added in the ''conf/config.xml'': To enable the following configuration section must be added in the ''conf/config.xml'':
- 
 <code xml> <code xml>
 <?xml version="1.0" encoding="UTF-8" ?> <?xml version="1.0" encoding="UTF-8" ?>
Line 43: Line 45:
             <attributes>             <attributes>
                 <attribute ident="description" type="text" target="description" />                 <attribute ident="description" type="text" target="description" />
-                <attribute ident="feedback_type" type="string" target="customfield_10101" /> +                <!-- The following fields could be enabled if you want the users to provide more data with every feedback item: --> 
-                <attribute ident="impacted_org" type="string" target="customfield_10102" />+                <!--
                 <attribute ident="annual_savings" type="string" target="customfield_10100" />                 <attribute ident="annual_savings" type="string" target="customfield_10100" />
-                <attribute ident="submitter_review" type="string" target="customfield_10103" />+                <attribute ident="priority" type="string" target="customfield_10101" /> 
 +                -->
             </attributes>             </attributes>
  
Line 69: Line 72:
 </stages-config> </stages-config>
 </code> </code>
- 
  
 ==== Stages metamodel ==== ==== Stages metamodel ====
Line 100: Line 102:
  
 As last step you have to provide translations for the introduced custom fields. The translation property consists of the prefix ''process.feedback.mapping.'' and the ident you defined in the config.xml file. For the example the translations are: As last step you have to provide translations for the introduced custom fields. The translation property consists of the prefix ''process.feedback.mapping.'' and the ident you defined in the config.xml file. For the example the translations are:
- 
 <code properties> <code properties>
 process.feedback.mapping.summary = Summary process.feedback.mapping.summary = Summary
 process.feedback.mapping.description = Description process.feedback.mapping.description = Description
-process.feedback.mapping.feedback_type = Feedback Type +process.feedback.mapping.annual_savings = Estimated annual savings 
-process.feedback.mapping.impacted_org  = Impact +process.feedback.mapping.priority = Priority
-process.feedback.mapping.annual_savings = Savings +
-process.feedback.mapping.submitter_review = Submitter+
 </code> </code>