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

Skip to content

Commit 04ca68f

Browse files
committed
Merge branch 'master' of github.com:Hacker0x01/docs.hackerone.com
2 parents f53dfe5 + 530edd3 commit 04ca68f

6 files changed

+45
-2
lines changed

.gitlab-ci.yml

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
stages:
2+
- deploy
3+
4+
deploy_production:
5+
stage: deploy
6+
tags:
7+
- runner-medium
8+
environment:
9+
name: production
10+
url: https://docs.hackerone.com
11+
image: node:11
12+
script:
13+
- echo "Deploy to production server"
14+
- yarn install
15+
- yarn deploy
16+
only:
17+
- master

docs/changelog/2019/may.md

Lines changed: 28 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,33 @@ path: "/changelog/2019/may"
44
date: "2019-05"
55
---
66

7-
### Program Dashboard
8-
We’ve revamped the Program Dashboard with new metric tables and charts that give better insight into reporting and analytics for programs.
7+
### Program Dashboard
8+
We’ve revamped the Program Dashboard with new metric tables and charts that give better insight into reporting and analytics for programs.
99

1010
![program dashboard](./images/may_2019_program_dashboard.png)
11+
12+
### Enhancements to the Jira Integration
13+
We've added these improvements to the bi-directional Jira integration:
14+
15+
#### 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
20+
21+
![additional fields wen escalating HackerOne to Jira](./images/may_2019_jira++_additional-fields.png)
22+
23+
#### 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.
25+
26+
![synchronize attachments option in the jira integration](./images/may_2019_jira++_sync-attachments.png)
27+
28+
#### Automated Report Closure
29+
Jira users can now select which Jira closed issue status should result in the closure of the HackerOne report.
30+
31+
![automating report closure with Jira](./images/may_2019_jira++_report-closure.png)
32+
33+
#### Severity to Priority Mapping
34+
With severity to priority mapping, Jira users can map HackerOne severity ratings to the priority fields they have in Jira. This enables the right priority to be set when escalating a report to Jira.
35+
36+
![severity to priority mapping](./images/may_2019_jira++_severity-priority-mapping.png)

0 commit comments

Comments
 (0)