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
72:jira_feedback [2018/10/16 17:23] – emr72:jira_feedback [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 8: Line 8:
 ==== Jira ==== ==== Jira ====
  
-First of all, create a Jira project where the feedback will be collected. If you want to collect more information than the summary and a description, you have to [[https://confluence.atlassian.com/adminjiraserver/adding-a-custom-field-938847222.html|add custom fields to your Jira project]] and add them to your ''Create Issue Screen''.+First of all, create a Jira project where the feedback will be collected. If you want to collect more information than the summary and a description, you have to [[https://confluence.atlassian.com/adminjiraserver/adding-a-custom-field-938847222.html|add custom fields to your Jira project]] and add them to your ''Create Issue Screen''. To locate the correct fields, use the Jira assistant "Where is my field?" for more info.
  
 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 config.xml ==== 
  
-To enable the following configuration section must be added in the ''conf/config.xml'':+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.
  
-xml+==== Stages config.xml ====
  
-<code file>+To enable the following configuration section must be added in the ''conf/config.xml'': 
 +<code xml>
 <?xml version="1.0" encoding="UTF-8" ?> <?xml version="1.0" encoding="UTF-8" ?>
 <stages-config> <stages-config>
Line 45: 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 76: Line 77:
 The feedback widget must be added to your Stages metamodel. The XML-Element is: The feedback widget must be added to your Stages metamodel. The XML-Element is:
  
-xml +<code xml>
- +
-<code file>+
 <widget:feedback/> <widget:feedback/>
 </code> </code>
Line 84: Line 83:
 For adding the widget to the social section, you can adopt it like this: For adding the widget to the social section, you can adopt it like this:
  
-xml +<code xml>
- +
-<code file>+
 <widget:definition id="social"> <widget:definition id="social">
     <layout:tabbed-card id="info">     <layout:tabbed-card id="info">
Line 105: 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>
-properties +
- +
-<code file>+
 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>