You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/programs/jira-cloud-integration.md
+29-5Lines changed: 29 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -10,22 +10,46 @@ To integrate with Jira Cloud:
10
10
1. Go to **Settings > Program > Integrations**.
11
11
2. Click the **Connect with JIRA** link.
12
12

13
+
13
14
3. Choose **JIRA Cloud**, and you'll be redirected to Atlassian Marketplace where you can download the HackerOne for JIRA application.
15
+
14
16

17
+
15
18
4. Click the **Get it now** button in Atlassian Marketplace to install the HackerOne for Jira application. The page will redirect you to your Jira instance and the integration will be downloaded and installed.
19
+
16
20

21
+
17
22
5. Click the **Get started** button on the installation confirmation pop-up.
23
+
18
24

25
+
19
26
6. The installation process will continue on the HackerOne website and will ask you to select the program you want to link to. Select the program you want to link to your Jira instance.
27
+
20
28

29
+
21
30
7. The set up will take you to the Jira settings page where you can select which events you want to sync between HackerOne and Jira.
22
31
23
32
With Jira integration, you can create Jira issues right from your HackerOne report.
24
33
25
-
### Create Jira Issues from your HackerOne Report
34
+
### How it works
26
35
To create Jira issues from your HackerOne report:
27
-
1. In the comments section of your report, change **Add comment** to **Change state > Triaged**.
28
-
2. Click the **Create JIRA issue** button to create the issue in Jira.
36
+
1. Go to the report you want to create a Jira issue for.
When you perform an action on the Jira report such as adding a comment or changing the status of the report, Hackbot will generate an internal comment on the HackerOne report to reflect the changes.
29
54
30
-
Every time an action occurs on the Jira issue, Hackbot will automatically create an internal comment on the HackerOne report.
Copy file name to clipboardExpand all lines: docs/programs/jira-server-integration.md
+9-1Lines changed: 9 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -17,15 +17,23 @@ To integrate with Jira Server:
17
17

18
18
19
19
4. Navigate to the Application Links console of JIRA by going to **JIRA Administration > Applications > Application Links**.
20
+
21
+
> **Note:** You must be a Jira administrator in order to set up and access the Jira integration settings. After you set up your integration, you can go back to regular access on Jira.
22
+
20
23

24
+
21
25
5. Enter `https://hackerone.com` and click **Create new link**.
22
26

27
+
23
28
6. Enter `https://hackerone.com` in the New URL field in the Configure Application URL window.
24
29

30
+
25
31
7. Enter `HackerOne` for the Application Name and select `Generic Application` in the Link applications window and click **Continue**.
26
32

33
+
27
34
8. Select the pencil icon for HackerOne on the Configure Application Links page.
28
35

36
+
29
37
9. Enter the following information on the Application Details section of the Configure HackerOne window:
30
38
31
39
Field | Details
@@ -75,7 +83,7 @@ State Changes | When someone changes the state of a report, post an update on th
75
83
Rewards | When someone awards or suggests a bounty and/or bonus, post an update on the associated Jira issue.
76
84
Assignee Changes | When someone assigns a user/group to a report, post an update on the associated Jira issue.
77
85
Disclosure | When disclosure is requested or a report becomes public, post an update on the associated Jira issue.
78
-
Synchronize attachments | *(Currently in beta)* Synchronize attachments linked with reports and comments to the associated Jira issue.
86
+
Synchronize attachments | *(Currently in beta)* Synchronize attachments linked with reports and comments to the associated Jira issue.
0 commit comments