Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
75:process_feedback_jira [2020/01/23 14:14] – created fnpk | 75:process_feedback_jira [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 32: | Line 32: | ||
<!-- The summary field will always be available and is automatically mapped to the Jira " | <!-- The summary field will always be available and is automatically mapped to the Jira " | ||
- | <!-- | + | <!-- |
- | | + | |
- | - The " | + | |
- | - The " | + | |
- The " | - The " | ||
- Optional: The targetType defines the type of the Jira field. Supported Jira fields see below. | - Optional: The targetType defines the type of the Jira field. Supported Jira fields see below. | ||
Line 41: | Line 39: | ||
< | < | ||
< | < | ||
- | <!-- The following fields could be enabled if you want the users to provide more data with every feedback item: --> | ||
- | <!-- | ||
- | < | ||
- | < | ||
- | < | ||
- | --> | ||
</ | </ | ||
<!-- | <!-- | ||
- | | + | |
- | - elementUrl e.g. https:// | + | |
- | - workspaceName e.g. " | + | |
- | - workspacePath e.g. " | + | |
- | - creatorFullname "John Doe" | + | |
- | - creatorUsername " | + | |
The " | The " | ||
Optional: The targetType defines the type of the Jira field. Supported Jira fields see below. | Optional: The targetType defines the type of the Jira field. Supported Jira fields see below. | ||
Line 66: | Line 53: | ||
< | < | ||
</ | </ | ||
+ | |||
+ | <!-- | ||
+ | See common feedback documentation | ||
+ | The " | ||
+ | Optional: The targetType defines the type of the Jira field. Supported Jira fields see below. | ||
+ | --> | ||
+ | < | ||
+ | < | ||
+ | </ | ||
</ | </ | ||
</ | </ | ||
Line 71: | Line 67: | ||
</ | </ | ||
- | ==== Supported Jira fields | + | ==== Basic Authentication ==== |
+ | |||
+ | You need credentials for a (technical) user who is allowed to create issues in the Jira project. | ||
+ | |||
+ | <code xml> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | === Jira Server === | ||
+ | * The '' | ||
+ | * [[https:// | ||
+ | === Jira Cloud === | ||
+ | In Jira cloud there are no usernames. The '' | ||
+ | |||
+ | ==== Supported Jira fields ==== | ||
* Description: | * Description: | ||
* Text Field (single line): '' | * Text Field (single line): '' | ||
* Text Field (multi line): '' | * Text Field (multi line): '' | ||
+ | * URL Field: '' | ||
* Select List (single choice): '' | * Select List (single choice): '' | ||
- | * Components: '' | + | |
+ | * Assignee: '' | ||
+ | * Reporter: '' | ||
+ | | ||
- | 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 | ||
+ | * 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:// | ||
Other Jira fields are not supported at the moment. | Other Jira fields are not supported at the moment. | ||
- | ==== 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 ''< | 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 ''< | ||
Line 89: | Line 108: | ||
</ | </ | ||
- | ==== Proxy ==== | + | ==== Proxy (Optional) |
You can specify a proxy server. | You can specify a proxy server. | ||
Line 100: | Line 119: | ||
</ | </ | ||
- | ==== OAuth 2.0 Password Grant ==== | + | ==== OAuth 2.0 Password Grant (Optional) |
We support also OAuth 2.0 with Password Grant. To configure it there are different properties: | We support also OAuth 2.0 with Password Grant. To configure it there are different properties: | ||
Line 127: | Line 146: | ||
</ | </ | ||
- | ==== Custom Header ==== | + | ==== Custom Header |
You can set custom header to the Jira-REST-Requests. | You can set custom header to the Jira-REST-Requests. | ||
Line 136: | Line 155: | ||
</ | </ | ||
+ | ==== Troubleshooting ==== | ||
+ | |||
+ | If the username/ | ||
+ | |||
+ | 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" | ||
+ | |