File tree Expand file tree Collapse file tree 4 files changed +25
-0
lines changed Expand file tree Collapse file tree 4 files changed +25
-0
lines changed Original file line number Diff line number Diff line change @@ -31,3 +31,28 @@ A HackerOne report gets triaged and escalated into Jira.
31
31
32
32
Hackbot automatically captures the status change and posts an internal comment on the associated HackerOne report.
33
33
![ jira-integration-2] ( ./images/jira-cloud-4.png )
34
+
35
+ #### Linking HackerOne Reports to Existing Jira Tasks
36
+ You can link your HackerOne reports to existing Jira tasks.
37
+
38
+ To link your reports:
39
+ 1 . Go to the HackerOne report in your inbox that you want to link to Jira.
40
+ 2 . Click ** Edit** next to <i >References</i >.
41
+
42
+ ![ link to jira-1] (./images/link jira-1.png)
43
+
44
+ 3 . Enter the Jira ticket reference ID in the ** Link JIRA ticket** field.
45
+ 4 . Click ** Link JIRA issue** .
46
+
47
+ ![ link to jira-2] ( ./images/link-jira-2.png )
48
+
49
+ The HackerOne report will now be linked to the Jira task.
50
+
51
+ There's also another way you can link your HackerOne reports to Jira. You can:
52
+ 1 . Go to the bottom of your HackerOne report.
53
+ 2 . Select ** Change state > Triaged** in the action picker.
54
+
55
+ ![ link to jira-3] ( ./images/link-jira-3.png )
56
+
57
+ 3 . Enter the JIRA ticket number in the ** Enter JIRA ticket #** field.
58
+ 4 . Click ** Link JIRA issue** .
You can’t perform that action at this time.
0 commit comments