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
Next revisionBoth sides next revision
75:process_feedback_jira [2021/07/07 08:37] – old revision restored (2021/05/12 16:50) fnpk75:process_feedback_jira [2021/08/05 12:35] – [Supported Jira fields] fnpk
Line 82: Line 82:
 In Jira cloud there are no usernames. The ''username'' is the mail address (e.g. ''user@example.com''). The **password is a API-Token** and not the password of the user. You can create a Token in your [[https://id.atlassian.com/manage-profile/security/api-tokens|Atlassian Account Management]]. In Jira cloud there are no usernames. The ''username'' is the mail address (e.g. ''user@example.com''). The **password is a API-Token** and not the password of the user. You can create a Token in your [[https://id.atlassian.com/manage-profile/security/api-tokens|Atlassian Account Management]].
  
-==== Supported Jira fields =====+==== Supported Jira fields ====
   * Description: ''targetType=""'' (Empty)   * Description: ''targetType=""'' (Empty)
   * Text Field (single line): ''targetType=""'' (Empty)   * Text Field (single line): ''targetType=""'' (Empty)
Line 89: Line 89:
   * Select List (single choice): ''targetType="selectList-singleChoice"''   * Select List (single choice): ''targetType="selectList-singleChoice"''
   * User Picker (single user): ''targetType="user-singleChoice"'' (Only Jira Server, not Jira Cloud)   * User Picker (single user): ''targetType="user-singleChoice"'' (Only Jira Server, not Jira Cloud)
-  * Assignee: ''targetType="user-singleChoice"'' (Only Jira Server, not Jira Cloud) +  * Assignee: ''target="assignee" targetType="user-singleChoice"'' (Only Jira Server, not Jira Cloud) 
-  * Reporter: ''targetType="user-singleChoice"'' (Only Jira Server, not Jira Cloud) +  * Reporter: ''target="reporter" targetType="user-singleChoice"'' (Only Jira Server, not Jira Cloud) 
-  * Components: ''targetType="components"''+  * Components: ''target="components" targetType="components"''
  
 **Be aware**: **Be aware**:
Line 154: Line 154:
 </code> </code>
  
 +==== Troubleshooting ====
 +
 +If the username/​password settings are not correct or the password is changed on the Jira side, but not in Stages, Jira might lock the account after a few tries. This will result in a "HTTP 403 Forbidden"​ error in stages.log.
 +
 +In that case, the Jira account needs to be unlocked again. Log into Jira as an administrator and follow these steps:
 +  * Click on the Gear icon in the upper right of Jira
 +  * Select "User Management"
 +  * Find the right user
 +  * Click on the "Reset Failed Login Count" link in the "Login Details"​ column.
 +