Stages Documentation

Differences

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

Link to this comparison view

Next revision		Previous revision
Next revisionBoth sides next revision
75:process_feedback_jira [2020/01/23 14:14] – created fnpk75:process_feedback_jira [2020/04/09 09:26] – fnpk
Line 69: Line 69:
   </feedback-system>   </feedback-system>
 </stages-config> </stages-config>
 +
 </code> </code>
  
-==== Supported Jira fields ===== +==== Supported Jira fields ==== 
-  * Description: ''targetType=""'' (Empty) + 
-  * Text Field (single line): ''targetType=""'' (Empty) +  * Description: ''targetType=_ckgedit_QUOT__ckgedit>'' (Empty) * Text Field (single line): ''targetType=_ckgedit_QUOT__ckgedit>''  (Empty) 
-  * Text Field (multi line): ''targetType=""'' (Empty)+  * Text Field (multi line): ''targetType=_ckgedit_QUOT__ckgedit>'' (Empty) * URL Field: ''targetType=_ckgedit_QUOT__ckgedit>''  (Empty)
   * Select List (single choice): ''targetType="selectList-singleChoice"''   * Select List (single choice): ''targetType="selectList-singleChoice"''
 +  * User Picker (single user): ''targetType="user-singleChoice"''
 +  * Assignee: ''targetType="user-singleChoice"''
 +  * Reporter: ''targetType="user-singleChoice"''
   * Components: ''targetType="components"''   * Components: ''targetType="components"''
  
-Be aware: If you choose Select or Component then the user entered values must be configured in Jira. Otherwise the ticket creation will fail.+**Be aware**: 
 + 
 +  * If you choose **Select**  or **Component**  then the user entered values must be configured in Jira. Otherwise the ticket creation will fail. 
 +  * If you choose **User Picker**, **Assignee**  or **Reporter**  then the users must be vald Jira user. Otherwise the ticket creation will fail. 
 +  * To set the **Reporter**  field it is [[https://community.atlassian.com/t5/Answers-Developer-Questions/Re-Assigning-a-reporter-when-creating-an-issue-with-rest/qaq-p/475645/comment-id/13300#M13300|mandatory to grant "Modify Reporter" to the technical user]]. Otherwise the ticket creation will fail.
  
 Other Jira fields are not supported at the moment. Other Jira fields are not supported at the moment.
Line 84: Line 92:
 ==== Custom Endpoint ==== ==== Custom Endpoint ====
  
-If your Jira REST-Endpiont differs from the standard location, you can specify it. If your link to the Jira-API is for example like ''<nowiki>https://api.example.com/example/api/2/issue</nowiki>'' then you have to specify ''<nowiki>https://api.example.com/example/</nowiki>'' as value for this property.+If your Jira REST-Endpiont differs from the standard location, you can specify it. If your link to the Jira-API is for example like ''<nowiki>https://api.example.com/example/api/2/issue</nowiki>''  then you have to specify ''<nowiki>https://api.example.com/example/</nowiki>''  as value for this property. 
 <code xml> <code xml>
 <property name="jira.rest.endpoint" value="https://api.example.com/example/" /> <property name="jira.rest.endpoint" value="https://api.example.com/example/" />
 +
 </code> </code>
  
Line 98: Line 108:
 <property name="proxy.port" value="3128" /> <property name="proxy.port" value="3128" />
 <property name="proxy.hostname" value="proxy.example.com" /> <property name="proxy.hostname" value="proxy.example.com" />
 +
 </code> </code>
  
Line 125: Line 136:
 <!-- OAuth 2.0 password --> <!-- OAuth 2.0 password -->
 <property name="authentication.oauth20.password" value="" /> <property name="authentication.oauth20.password" value="" />
 +
 </code> </code>
  
Line 134: Line 146:
 <property name="jira.rest.customheader.key" value="" /> <property name="jira.rest.customheader.key" value="" />
 <property name="jira.rest.customheader.value" value="" /> <property name="jira.rest.customheader.value" value="" />
 +
 </code> </code>
 +