Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
72:jira_feedback [2018/10/24 11:19] – Code formatting fnpk | 72: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, | + | 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, |
To configure Stages, ids of the Jira custom fields are required. There are several ways to find them out in the [[https:// | To configure Stages, ids of the Jira custom fields are required. There are several ways to find them out in the [[https:// | ||
+ | |||
+ | Stages will use the Jira REST interface to create the issue. [[https:// | ||
+ | |||
==== Stages config.xml ==== | ==== Stages config.xml ==== | ||
To enable the following configuration section must be added in the '' | To enable the following configuration section must be added in the '' | ||
- | + | <code xml> | |
- | <file xml> | + | |
<?xml version=" | <?xml version=" | ||
< | < | ||
Line 43: | Line 45: | ||
< | < | ||
< | < | ||
- | <attribute ident=" | + | <!-- The following fields could be enabled if you want the users to provide more data with every feedback item: --> |
- | <attribute ident=" | + | <!-- |
< | < | ||
- | < | + | < |
+ | --> | ||
</ | </ | ||
Line 68: | Line 71: | ||
</ | </ | ||
</ | </ | ||
- | </file> | + | </code> |
==== Stages metamodel ==== | ==== Stages metamodel ==== | ||
Line 74: | 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: | ||
- | <file xml> | + | <code xml> |
< | < | ||
- | </file> | + | </code> |
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: | ||
- | <file xml> | + | <code xml> |
< | < | ||
< | < | ||
Line 94: | Line 97: | ||
</ | </ | ||
</ | </ | ||
- | </file> | + | </code> |
==== Stages language properties ==== | ==== Stages language properties ==== | ||
As last step you have to provide translations for the introduced custom fields. The translation property consists of the prefix '' | As last step you have to provide translations for the introduced custom fields. The translation property consists of the prefix '' | ||
- | + | <code properties> | |
- | properties | + | |
- | + | ||
- | <file 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 | + | process.feedback.mapping.priority |
- | process.feedback.mapping.annual_savings = Savings | + | </code> |
- | process.feedback.mapping.submitter_review | + | |
- | </file> | + | |
After all, don't forget to execute '' | After all, don't forget to execute '' | ||