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 revisionBoth sides next revision
72:jira_feedback [2019/01/29 14:16] – Fixt syntax highlighting fnpk72:jira_feedback [2019/04/24 16:46] – emr
Line 14: Line 14:
  
 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 42:
             <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 69:
 </stages-config> </stages-config>
 </code> </code>
- 
  
 ==== Stages metamodel ==== ==== Stages metamodel ====
Line 100: Line 99:
  
 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