Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b49ac87

Browse files
committed
fixed error in jira additional fields
1 parent 0a41b8d commit b49ac87

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

docs/changelog/2019/may.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,12 @@ We’ve revamped the Program Dashboard with new metric tables and charts that gi
1313
We've added these improvements to the bi-directional Jira integration:
1414

1515
#### Additional Fields
16-
The HackerOne to Jira escalation template now includes these additional fields so that Jira users can have all fields in Jira be mapped to a value from the HackerOne report:
17-
* CVSS (shows only when Bug is selected issue type)
18-
* Due date
19-
* Environment
16+
The HackerOne to Jira escalation template now includes all additional fields that are either a type of `string`, `number`, or `date`. This enables Jira users to have all fields in Jira be mapped to a value from the HackerOne report. All available Jira fields will automatically be pulled from the selected issue type.
2017

2118
![additional fields wen escalating HackerOne to Jira](./images/may_2019_jira++_additional-fields.png)
2219

2320
#### Sync Attachments
24-
Jira users can now sync attachments from their HackerOne report to Jira by selecting **Synchronize attachments** in the **Select HackerOne to JIRA events** section when configuring their Jira integration.
21+
Jira users can now sync attachments from their HackerOne report to Jira by selecting **Synchronize attachments** in the **Select HackerOne to JIRA events** section when configuring their Jira integration.
2522

2623
![synchronize attachments option in the jira integration](./images/may_2019_jira++_sync-attachments.png)
2724

0 commit comments

Comments
 (0)