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

Skip to content

Commit 910b311

Browse files
authored
Create jira-integration.md
1 parent fdfc5b9 commit 910b311

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed

docs/programs/jira-integration.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
title: "Jira Integration"
3+
path: "/programs/jira-integration.html"
4+
id: "programs/jira-integration"
5+
---
6+
7+
HackerOne enables you to set up a bi-directional Jira integration. This means that Jira users can sync specific workflows from Jira to HackerOne and vice versa, from HackerOne to Jira. There's no need to go back and forth between Jira and HackerOne. With this integration, valid bug reports become task assignments in JIRA with a single click, and fixed bugs automatically come back as being marked as resolved. This integration helps your development and security teams stay aligned, and contributes to a better workflow to process security vulnerabilities.
8+
9+
improves the collaboration between various teams by making it easier to review information across teams and tools.
10+
11+
These events and directions are currently supported through the bi-directional Jira integration:
12+
13+
HackerOne to Jira | Jira to HackerOne
14+
----------------- | -------------------
15+
Comments | Coments
16+
State changes | State changes
17+
Rewards | Resolution changes
18+
Asignee changes | Asignee changes
19+
Public disclosure | Priority changes
20+
21+
You can choose to integrate from 2 different types of Jira integration:
22+
* Jira Server
23+
* Jira Cloud
24+
25+
### How it Works
26+
A HackerOne report gets triaged and escalated into Jira.
27+
![jira-integration-1](./images/jira-integration.png)
28+
29+
Hackbot automatically captures the status change and posts an internal comment on the associated HackerOne report.
30+
![jira-integration-2](./images/jira-cloud-4.png)

0 commit comments

Comments
 (0)