8000 updated integration stuff with new add ref button · csit-github/docs.hackerone.com@629f2e3 · GitHub
[go: up one dir, main page]
Skip to content

Commit 629f2e3

Browse files
stacyspivastacyspiva
committed
updated integration stuff with new add ref button
1 parent e3e7f29 commit 629f2e3

11 files changed

+111
-45
lines changed

‎docs/programs/assembla-integration.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,14 @@ With all of the provided information, HackerOne will be able to set up your requ
1919
After your Assembla integration has been set up:
2020
1. Change the action picker to **Change state > Triaged** in your report.
2121

22-
![integrations](./images/integrations.png)
22+
![integrations](./images/add-integration-reference.png)
2323

24-
2. Click **Escalate**.
25-
3. You’ll be taken to your Assembla account where the report is pre-populated. Submit the issue to create the report in Assembla.
26-
4. Copy the Assembla report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in Assembla.
24+
2. Click **Add reference to issue tracker**.
25+
3. Make sure your Assembla integration is selected.
26+
27+
![integration](./images/issue-tracker-reference.png)
28+
29+
4. Click **Generate escalation**. You’ll be taken to your Assembla account where the report is pre-populated.
30+
3. Submit the issue to create the report in Assembla.
31+
4. Copy the Assembla report issue number and paste it in the **Reference ID** field back in the HackerOne.
32+
5. Click **Create** to create a direct reference link to the issue in Assembla.

‎docs/programs/bugzilla-integration.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,14 @@ With all of the provided information, HackerOne will be able to set up your requ
1919
After your Bugzilla integration has been set up:
2020
1. Change the action picker to **Change state > Triaged** in your report.
2121

22-
![integrations](./images/integrations.png)
22+
![integrations](./images/add-integration-reference.png)
2323

24-
2. Click **Escalate**.
25-
3. You’ll be taken to your Bugzilla account where the report is pre-populated. Submit the issue to create the report in Bugzilla.
26-
4. Copy the Bugzilla report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in Bugzilla.
24+
2. Click **Add reference to issue tracker**.
25+
3. Make sure your Bugzilla integration is selected.
26+
27+
![integration](./images/issue-tracker-reference.png)
28+
29+
4. Click **Generate escalation**. You’ll be taken to your Bugzilla account where the report is pre-populated.
30+
3. Submit the issue to create the report in Bugzilla.
31+
4. Copy the Bugzilla report issue number and paste it in the **Reference ID** field back in the HackerOne.
32+
5. Click **Create** to create a direct reference link to the issue in Bugzilla.

‎docs/programs/freshdesk-integration.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,14 @@ With all of the provided information, HackerOne will be able to set up your requ
2222
After your Freshdesk integration has been set up:
2323
1. Change the action picker to **Change state > Triaged** in your report.
2424

25-
![integrations](./images/integrations.png)
25+
![integrations](./images/add-integration-reference.png)
2626

27-
2. Click **Escalate**.
28-
3. You’ll be taken to your Bugzilla account where the report is pre-populated. Submit the issue to create the report in Freshdesk.
29-
4. Copy the Freshdesk report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in Freshdesk.
27+
2. Click **Add reference to issue tracker**.
28+
3. Make sure your Freshdesk integration is selected.
29+
30+
![integration](./images/issue-tracker-reference.png)
31+
32+
4. Click **Generate escalation**. You’ll be taken to your Freshdesk account where the report is pre-populated.
33+
3. Submit the issue to create the report in Freshdesk.
34+
4. Copy the Freshdesk report issue number and paste it in the **Reference ID** field back in the HackerOne.
35+
5. Click **Create** to create a direct reference link to the issue in Freshdesk.

‎docs/programs/github-integration.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,14 @@ With all of the provided information, HackerOne will be able to set up your requ
2323
After your GitHub integration has been set up:
2424
1. Change the action picker to **Change state > Triaged** in your report.
2525

26-
![integrations](./images/integrations.png)
26+
![integrations](./images/add-integration-reference.png)
2727

28-
2. Click **Escalate**.
29-
3. You’ll be taken to your GitHub account where the report is pre-populated. Submit the issue to create the report in GitHub.
30-
4. Copy the GitHub report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in GitHub.
28+
2. Click **Add reference to issue tracker**.
29+
3. Make sure your GitHub integration is selected.
30+
31+
![integration](./images/issue-tracker-reference.png)
32+
33+
4. Click **Generate escalation**. You’ll be taken to your GitHub account where the report is pre-populated.
34+
3. Submit the issue to create the report in GitHub.
35+
4. Copy the GitHub report issue number and paste it in the **Reference ID** field back in the HackerOne.
36+
5. Click **Create** to create a direct reference link to the issue in GitHub.

‎docs/programs/gitlab-integration.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,14 @@ With all of the provided information, HackerOne will be able to set up your requ
2323
After your GitLab integration has been set up:
2424
1. Change the action picker to **Change state > Triaged** in your report.
2525

26-
![integrations](./images/integrations.png)
26+
![integrations](./images/add-integration-reference.png)
2727

28-
2. Click **Escalate**.
29-
3. You’ll be taken to your GitLab account where the report is pre-populated. Submit the issue to create the report in GitLab.
30-
4. Copy the GitLab report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in GitLab.
28+
2. Click **Add reference to issue tracker**.
29+
3. Make sure your GitLab integration is selected.
30+
31+
![integration](./images/issue-tracker-reference.png)
32+
33+
4. Click **Generate escalation**. You’ll be taken to your GitLab account where the report is pre-populated.
34+
3. Submit the issue to create the report in GitLab.
35+
4. Copy the GitLab report issue number and paste it in the **Reference ID** field back in the HackerOne.
36+
5. Click **Create** to create a direct reference link to the issue in GitLab.

‎docs/programs/ibm-resilient-integration.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ path: "/programs/ibm-resilient.html"
44
id: "programs/ibm-resilient"
55
---
66

7-
With the IBM Resilient web URL integration, you can push all of your HackerOne submissions to Resilient so that you can track all of your vulnerability reports on Resilient.
7+
With the IBM Resilient web URL integration, you can push all of your HackerOne submissions to Resilient so that you can track all of your vulnerability reports on Resilient.
88

99
In order to configure the IBM Resilient integration for your team, [contact HackerOne](https://support.hackerone.com/hc/en-us/requests/new) with the following information:
1010

@@ -17,8 +17,14 @@ With all of the provided information, HackerOne will be able to set up your requ
1717
After your Resilient integration has been set up:
1818
1. Change the action picker to **Change state > Triaged** in your report.
1919

20-
![integrations](./images/integrations.png)
20+
![integrations](./images/add-integration-reference.png)
2121

22-
2. Click **Escalate**.
23-
3. You'll be taken to your Resilient account where the report is pre-populated. Submit the issue to create the report in Resilient.
24-
4. Copy the Resilient report issue number and paste it in the Reference ID field of the HackerOne report to create a direct reference link to the issue in Resilient.
22+
2. Click **Add reference to issue tracker**.
23+
3. Make sure your Resilient integration is selected.
24+
25+
![integration](./images/issue-tracker-reference.png)
26+
27+
4. Click **Generate escalation**. You’ll be taken to your Resilient account where the report is pre-populated.
28+
3. Submit the issue to create the report in Resilient.
29+
4. Copy the Resilient report issue number and paste it in the **Reference ID** field back in the HackerOne.
30+
5. Click **Create** to create a direct reference link to the issue in Resilient.

‎docs/programs/mantisbt-integration.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,14 @@ With all of the provided information, HackerOne will be able to set up your requ
1919
After your MantisBT integration has been set up:
2020
1. Change the action picker to **Change state > Triaged** in your report.
2121

22-
![integrations](./images/integrations.png)
22+
![integrations](./images/add-integration-reference.png)
2323

24-
2. Click **Escalate**.
25-
3. You’ll be taken to your MantisBT account where the report is pre-populated. Submit the issue to create the report in MantisBT.
26-
4. Copy the MantisBT report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in MantisBT.
24+
2. Click **Add reference to issue tracker**.
25+
3. Make sure your MantisBT integration is selected.
26+
27+
![integration](./images/issue-tracker-reference.png)
28+
29+
4. Click **Generate escalation**. You’ll be taken to your MantisBT account where the report is pre-populated.
30+
3. Submit the issue to create the report in MantisBT.
31+
4. Copy the MantisBT report issue number and paste it in the **Reference ID** field back in the HackerOne.
32+
5. Click **Create** to create a direct reference link to the issue in MantisBT.

‎docs/programs/otrs-integration.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,14 @@ With all of the provided information, HackerOne will be able to set up your requ
1919
After your OTRS integration has been set up:
2020
1. Change the action picker to **Change state > Triaged** in your report.
2121

22-
![integrations](./images/integrations.png)
22+
![integrations](./images/add-integration-reference.png)
2323

24-
2. Click **Escalate**.
25-
3. You’ll be taken to your OTRS account where the report is pre-populated. Submit the issue to create the report in OTRS.
26-
4. Copy the OTRS report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in OTRS.
24+
2. Click **Add reference to issue tracker**.
25+
3. Make sure your OTRS integration is selected.
26+
27+
![integration](./images/issue-tracker-reference.png)
28+
29+
4. Click **Generate escalation**. You’ll be taken to your OTRS account where the report is pre-populated.
30+
3. Submit the issue to create the report in OTRS.
31+
4. Copy the OTRS report issue number and paste it in the **Reference ID** field back in the HackerOne.
32+
5. Click **Create** to create a direct reference link to the issue in OTRS.

‎docs/programs/redmine.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,14 @@ With all of the provided information, HackerOne will be able to set up your requ
1919
After your Redmine integration has been set up:
2020
1. Change the action picker to **Change state > Triaged** in your report.
2121

22-
![integrations](./images/integrations.png)
22+
![integrations](./images/add-integration-reference.png)
2323

24-
2. Click **Escalate**.
25-
3. You’ll be taken to your Redmine account where the report is pre-populated. Submit the issue to create the report in Redmine.
26-
4. Copy the Redmine report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in Redmine.
24+
2. Click **Add reference to issue tracker**.
25+
3. Make sure your Redmine integration is selected.
26+
27+
![integration](./images/issue-tracker-reference.png)
28+
29+
4. Click **Generate escalation**. You’ll be taken to your Redmine account where the report is pre-populated.
30+
3. Submit the issue to create the report in Redmine.
31+
4. Copy the Redmine report issue number and paste it in the **Reference ID** field back in the HackerOne.
32+
5. Click **Create** to create a direct reference link to the issue in Redmine.

‎docs/programs/trac-integration.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,14 @@ With all of the provided information, HackerOne will be able to set up your requ
1919
After your Trac integration has been set up:
2020
1. Change the action picker to **Change state > Triaged** in your report.
2121

22-
![integrations](./images/integrations.png)
22+
![integrations](./images/add-integration-reference.png)
2323

24-
2. Click **Escalate**.
25-
3. You’ll be taken to your Trac account where the report is pre-populated. Submit the issue to create the report in Trac.
26-
4. Copy the Trac report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in Trac.
24+
2. Click **Add reference to issue tracker**.
25+
3. Make sure your Trac integration is selected.
26+
27+
![integration](./images/issue-tracker-reference.png)
28+
29+
4. Click **Generate escalation**. You’ll be taken to your Trac account where the report is pre-populated.
30+
3. Submit the issue to create the report in Trac.
31+
4. Copy the Trac report issue number and paste it in the **Reference ID** field back in the HackerOne.
32+
5. Click **Create** to create a direct reference link to the issue in Trac.

‎docs/programs/zendesk-integration.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,14 @@ With all of the provided information, HackerOne will be able to set up your requ
2323
After your Zendesk integration has been set up:
2424
1. Change the action picker to **Change state > Triaged** in your report.
2525

26-
![integrations](./images/integrations.png)
26+
![integrations](./images/add-integration-reference.png)
2727

28-
2. Click **Escalate**.
29-
3. You’ll be taken to your Zendesk account where the report is pre-populated. Submit the issue to create the report in Zendesk.
30-
4. Copy the Zendesk report issue number and paste it in the **Reference ID** field of the HackerOne report to create a direct reference link to the issue in Zendesk.
28+
2. Click **Add reference to issue tracker**.
29+
3. Make sure your Zendesk integration is selected.
30+
31+
![integration](./images/issue-tracker-reference.png)
32+
33+
4. Click **Generate escalation**. You’ll be taken to your Zendesk account where the report is pre-populated.
34+
3. Submit the issue to create the report in Zendesk.
35+
4. Copy the Zendesk report issue number and paste it in the **Reference ID** field back in the HackerOne.
36+
5. Click **Create** to create a direct reference link to the issue in Zendesk.

0 commit comments

Comments
 (0)
0