10000 More details on the new Jira features · lanahkomputer/docs.hackerone.com@39b342a · GitHub
[go: up one dir, main page]
Skip to content

Commit 39b342a

Browse files
martijnrusschenmartijnrusschen
committed
More details on the new Jira features
1 parent c072514 commit 39b342a

File tree

1 file changed

+40
-19
lines changed

1 file changed

+40
-19
lines changed

‎docs/programs/jira-integration.md

Lines changed: 40 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -21,34 +21,22 @@ Jump to: |
2121
-------- |
2222
[Creating a Jira Issue](#creating) |
2323
[Linking HackerOne Reports to Existing Jira Tasks](#linking) |
24+
[Syncing updates from HackerOne to Jira](#hackerone-to-jira) |
25+
[Syncing updates from Jira to HackerOne](#jira-to-hackerone) |
26+
[Automaticly resolving a HackerOne report](#auto-close) |
2427
[Installing the Jira integration](#installing) |
2528
</div>
2629

27-
### How it Works
28-
A HackerOne report gets triaged and escalated into Jira.
29-
![jira-integration-1](./images/jira-integration.png)
30-
31-
Hackbot automatically captures the status change and posts an internal comment on the associated HackerOne report.
32-
![jira-integration-2](./images/jira-cloud-4.png)
33-
34-
These events and directions are currently supported through the bi-directional Jira integration:
35-
36-
HackerOne to Jira | Jira to HackerOne
37-
----------------- | -------------------
38-
Comments | Comments
39-
State changes | State changes<br><br>You can select which Jira state will result in automatic closure of the HackerOne report.
40-
Rewards | Resolution changes
41-
Assignee changes | Assignee changes
42-
Public disclosure | Priority changes
43-
Report attachments |
44-
4530
<h3 id="creating">Creating a Jira Issue</h3>
4631
You can create new Jira issues for reports you receive on HackerOne.
4732

4833
To create a new Jira issue from your HackerOne report:
4934
1. Go to the HackerOne report in your inbox that you want to create a new Jira issue for.
5035
2. Click **Edit** next to <i>References</i>.
51-
3. Click **Create JIRA issue**.
36+
3. Click **Create JIRA issue**. Optional: If the report contains any attachments, these will be synced to the Jira issue created as well.
37+
38+
![jira-integration-1](./images/jira-integration.png)
39+
5240
4. Select the project that you want the issue to link to in the dropdown. *Note: This option occurs only if you have multiple projects to select from. If you only have 1 project, the issue will automatically escalate to that project.*
5341

5442
![create jira issue](./images/create-jira.png)
@@ -90,6 +78,39 @@ There's also another way you can link your HackerOne reports to Jira. You can:
9078
3. Enter the JIRA ticket number in the **Enter JIRA ticket #** field.
9179
4. Click **Link JIRA issue**.
9280

81+
<h3 id="hackerone-to-jira">Syncing updates from HackerOne to Jira</h3>
82+
83+
With the Jira integration you can sync the following report updates to Jira. All updates on a report are synced as a comment to Jira:
84+
- Report Comments
85+
- State changes
86+
- Rewards
87+
- Assignee changes
88+
- Public disclosure
89+
90+
All actions are configureable and can be toggled from the Jira integration settings page.
91+
92+
If you're using [Custom Fields](/programs/custom-fields.html), you can use these in the integration. All Custom Fields automaticly appear as available variables that you can use to set up the field mapping between HackerOne and Jira.
93+
94+
<h3 id="jira-to-hackerone">Syncing updates from Jira to HackerOne</h3>
95+
96+
To make sure your security team stays up to date with the changes that happen in Jira, you can sync back activities from Jira to the HackerOne report. All updates from Jira will be reflected in HackerOne as an internal comment on the ascociated report.
97+
98+
![jira-cloud-works-5](./images/jira-cloud-works-5.png)
99+
100+
We currently support the following Jira activities:
101+
- Comments
102+
- State changes
103+
- Resolution changes
104+
- Assignee changes
105+
- Priority changes
106+
107+
You can choose which events you want to syncronize from the Jira integration settings page. Each of these activities can be toggled individually.
108+
109+
110+
111+
<h3 id="auto-close">Automaticly resolving a HackerOne report</h3>
112+
113+
You can choose to automaticly close a HackerOne report as "resolved" when a Jira issue closes. This helps you to close the loop in the HackerOne system and make sure the researcher is properly notified when closing the Jira issue that's linked to the report.
93114

94115
<h3 id="installing">Installing the Jira integration</h3>
95116

0 commit comments

Comments
 (0)
0