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
75:process_feedback_jira [2020/07/13 11:08] fnpk75:process_feedback_jira [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 78: Line 78:
  
 === Jira Server === === Jira Server ===
-The ''user'' and ''password'' are the normal username and password of the user.+  * The ''user'' and ''password'' are the normal username and password of the user. 
 +  * [[https://confluence.atlassian.com/enterprise/disabling-basic-authentication-1044776464.html|Basic authentication must not be deactivated]]
 === Jira Cloud === === Jira Cloud ===
 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 90:
   * 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 155:
 </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.
 +