From 72679ac926108088890dcd0d0d14247192abfba9 Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Tue, 20 Aug 2019 11:55:43 +0200 Subject: [PATCH 01/15] Add new question to FAQ --- docs/programs/jira-faqs.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/programs/jira-faqs.md b/docs/programs/jira-faqs.md index 530151ed956..9b64c02aeb5 100644 --- a/docs/programs/jira-faqs.md +++ b/docs/programs/jira-faqs.md @@ -9,4 +9,5 @@ Question | Answer The HackerOne markdown doesn't convert correctly to Jira. How can I convert the markdown correction to Jira? | You can use a Jira optimized template by setting the escalation template to: `{{details_custom_jira}}`. What fields are supported in the bi-directional Jira integration? | We support all fields that have the type: `string`, `number`, or `date`. I have multiple HackerOne programs. Can I integrate each of these programs to the same Jira instance? | Yes, you can integrate multiple HackerOne programs to the same Jira instance. If you're using Jira Cloud, you must first remove the "HackerOne for Jira" plugin and then follow steps 1-2 below.

To integrate Jira with multiple HackerOne programs: -My Jira is behind a firewall and is not externally accessible. How can I integrate with Jira? | To use the bi-directional Jira integration, you need to make sure your Jira instance is accessible from the HackerOne system. You can whitelist HackerOne’s IP addresses in your firewall to only open it up to the HackerOne application. Contact your program manager to request our IP addresses to whitelist in your firewall.

If you don't want to expose your Jira to HackerOne, [contact us](https://support.hackerone.com/hc/en-us/requests/new) to get a work-around that enables you to only escalate to Jira. +My Jira is behind a firewall and is not externally accessible. How can I integrate with Jira? | To use the bi-directional Jira integration, you need to make sure your Jira instance is accessible from the HackerOne system. You can whitelist HackerOne’s IP addresses in your firewall to only open it up to the HackerOne application. Contact your program manager to request our IP addresses to whitelist in your firewall.

If you don't want to expose your Jira to HackerOne, [contact us](https://support.hackerone.com/hc/en-us/requests/new) to get a work-around that enables you to only escalate to Jira. +I'm getting the following error when creating a Jira issue `JIRA returned the following error: "You must specify a summary of the issue.` | This means that you didn't specify a value for the `summary` field in your Jira integration settings. Please review the field mapping in your Jira integration settings and make sure values are provided for all required fields. From 044849188e3da27cf45c735abf3a509c521ea6de Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Tue, 20 Aug 2019 14:06:15 +0200 Subject: [PATCH 02/15] Improved styling --- docs/programs/jira-faqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/jira-faqs.md b/docs/programs/jira-faqs.md index 9b64c02aeb5..b3d64a435fd 100644 --- a/docs/programs/jira-faqs.md +++ b/docs/programs/jira-faqs.md @@ -10,4 +10,4 @@ The HackerOne markdown doesn't convert correctly to Jira. How can I convert the What fields are supported in the bi-directional Jira integration? | We support all fields that have the type: `string`, `number`, or `date`. I have multiple HackerOne programs. Can I integrate each of these programs to the same Jira instance? | Yes, you can integrate multiple HackerOne programs to the same Jira instance. If you're using Jira Cloud, you must first remove the "HackerOne for Jira" plugin and then follow steps 1-2 below.

To integrate Jira with multiple HackerOne programs: My Jira is behind a firewall and is not externally accessible. How can I integrate with Jira? | To use the bi-directional Jira integration, you need to make sure your Jira instance is accessible from the HackerOne system. You can whitelist HackerOne’s IP addresses in your firewall to only open it up to the HackerOne application. Contact your program manager to request our IP addresses to whitelist in your firewall.

If you don't want to expose your Jira to HackerOne, [contact us](https://support.hackerone.com/hc/en-us/requests/new) to get a work-around that enables you to only escalate to Jira. -I'm getting the following error when creating a Jira issue `JIRA returned the following error: "You must specify a summary of the issue.` | This means that you didn't specify a value for the `summary` field in your Jira integration settings. Please review the field mapping in your Jira integration settings and make sure values are provided for all required fields. +I'm getting the following error when creating a Jira issue: `JIRA returned the following error: "You must specify a summary of the issue."` | This means that you didn't specify a value for the `summary` field in your Jira integration settings. Please review the field mapping in your Jira integration settings and make sure values are provided for all required fields. \ No newline at end of file From 06820f1ea36359ee94509f1fc020f20984964cea Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Tue, 20 Aug 2019 14:15:41 +0200 Subject: [PATCH 03/15] Start with a Jira variables doc --- docs/programs/jira-variables.md | 30 ++++++++++++++++++++++++++++ src/pages/programs/programs-nav.yaml | 2 ++ 2 files changed, 32 insertions(+) create mode 100644 docs/programs/jira-variables.md diff --git a/docs/programs/jira-variables.md b/docs/programs/jira-variables.md new file mode 100644 index 00000000000..5f7518ad016 --- /dev/null +++ b/docs/programs/jira-variables.md @@ -0,0 +1,30 @@ +--- +title: "Jira Variables" +path: "/programs/jira-variables.html" +id: "programs/jira-variables" +--- + +Variable | Description | Example +-------- | ------ | ------ +`{{assignee}}` | The user that's assigned to the report. | +`{{days_after_report(days)}}` | +`{{details_custom_jira}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in a special Jira flavored markdown format. | +`{{details_markdown}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in markdown format. | +`{{details_truncated}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format truncated at 4,000 characters. +`{{details}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format. | +`{{due_date(days_from_now)}}` | +`{{email_local_part}}` | The local part of the user creating the Jira issue. The local part of an email address is the part before the @ symbol. +`{{email}}` | The email address of the user creating the Jira issue | +`{{escalation_time}}` | The date and time of when the report was escalated to Jira. | +`{{jira_severity}}` | +`{{report_id}}` | The ID of the report | +`{{report_link}}` | The url of the report | +`{{reporter_link}}` | The url of the researcher's HackerOne profile | +`{{reporter_name}}` | The name of the researcher that reported the vulnerability (this will fallback to the username if the researcher didn't provide their name) | +`{{reporter_username}}` | The username of the researcher that reported the vulnerability | +`{{submission_date_custom_format}}` | +`{{submission_date_y_m_d}}` | +`{{submission_date}}` | The created date of the report | +`{{title}}` | The title of the report | +`{{vulnerability_information}}` | The description of the vulnerability in the report. | +`{{weakness}}` | The CWE weakness of the report | diff --git a/src/pages/programs/programs-nav.yaml b/src/pages/programs/programs-nav.yaml index cd4985f7668..2947c5a4677 100644 --- a/src/pages/programs/programs-nav.yaml +++ b/src/pages/programs/programs-nav.yaml @@ -172,6 +172,8 @@ path: /programs/jira-cloud-integration.html - title: Jira Server Setup path: /programs/jira-server-integration.html + - title: Jira Variables + path: /programs/jira-variables.html - title: Jira FAQs path: /programs/jira-faqs.html - title: MantisBT From 3dbe9e84e80c131bd923dcab7708d1ed2f8d0076 Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 12:35:15 +0200 Subject: [PATCH 04/15] Make variables page a global page --- .../{jira-variables.md => integration-variables.md} | 6 +++--- docs/programs/jira-faqs.md | 1 + src/pages/programs/programs-nav.yaml | 4 ++-- 3 files changed, 6 insertions(+), 5 deletions(-) rename docs/programs/{jira-variables.md => integration-variables.md} (94%) diff --git a/docs/programs/jira-variables.md b/docs/programs/integration-variables.md similarity index 94% rename from docs/programs/jira-variables.md rename to docs/programs/integration-variables.md index 5f7518ad016..4876be2fbbb 100644 --- a/docs/programs/jira-variables.md +++ b/docs/programs/integration-variables.md @@ -1,7 +1,7 @@ --- -title: "Jira Variables" -path: "/programs/jira-variables.html" -id: "programs/jira-variables" +title: "Integration Variables" +path: "/programs/integration-variables.html" +id: "programs/integration-variables" --- Variable | Description | Example diff --git a/docs/programs/jira-faqs.md b/docs/programs/jira-faqs.md index ab4e3b20b32..412908bd3a2 100644 --- a/docs/programs/jira-faqs.md +++ b/docs/programs/jira-faqs.md @@ -8,6 +8,7 @@ Question | Answer -------- | ------ The HackerOne markdown doesn't convert correctly to Jira. How can I convert the markdown correction to Jira? | You can use a Jira optimized template by setting the escalation template to: `{{details_custom_jira}}`. What fields are supported in the bi-directional Jira integration? | We support all fields that have the type: `string`, `number`, `date`, `Radio Buttons`, or `Select List (single choice)`. +What do the different variables mean? | Please refer to the [Integration variables](integration-variables.html) page to see examples and descriptions of each variable. I have multiple HackerOne programs. Can I integrate each of these programs to the same Jira instance? | Yes, you can integrate multiple HackerOne programs to the same Jira instance. If you're using Jira Cloud, you must first remove the "HackerOne for Jira" plugin and then follow steps 1-2 below.

To integrate Jira with multiple HackerOne programs:
    1. Follow all of the [Jira Server steps](jira-server-integration.html) for the first program you want to integrate.
    2. For each subsequent program you need to add an integration for, only follow steps 12-16 in [the Jira Server article](jira-server-integration.html).
    • You only need to follow steps 12-16 because the application link has already been created when integrating with your first program, and only 1 application link is needed to set up a Jira integration.
My Jira is behind a firewall and is not externally accessible. How can I integrate with Jira? | To use the bi-directional Jira integration, you need to make sure your Jira instance is accessible from the HackerOne system. You can whitelist HackerOne’s IP addresses in your firewall to only open it up to the HackerOne application. Contact your program manager to request our IP addresses to whitelist in your firewall.

If you don't want to expose your Jira to HackerOne, [contact us](https://support.hackerone.com/hc/en-us/requests/new) to get a work-around that enables you to only escalate to Jira. I'm getting the following error when creating a Jira issue: `JIRA returned the following error: "You must specify a summary of the issue."` | This means that you didn't specify a value for the `summary` field in your Jira integration settings. Please review the field mapping in your Jira integration settings and make sure values are provided for all required fields. \ No newline at end of file diff --git a/src/pages/programs/programs-nav.yaml b/src/pages/programs/programs-nav.yaml index 2947c5a4677..c27bdda49a3 100644 --- a/src/pages/programs/programs-nav.yaml +++ b/src/pages/programs/programs-nav.yaml @@ -149,6 +149,8 @@ items: - title: Supported Integrations path: /programs/supported-integrations.html + - title: Integration Variables + path: /programs/integration-variables.html - title: Email Forwarding path: /programs/email-forwarding.html - title: Embedded Submission Form @@ -172,8 +174,6 @@ path: /programs/jira-cloud-integration.html - title: Jira Server Setup path: /programs/jira-server-integration.html - - title: Jira Variables - path: /programs/jira-variables.html - title: Jira FAQs path: /programs/jira-faqs.html - title: MantisBT From 3811fb3d7029344f814469d0503393d4b08282b9 Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 12:53:44 +0200 Subject: [PATCH 05/15] Remove examples column --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 4876be2fbbb..57d8343e55b 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -5,7 +5,7 @@ id: "programs/integration-variables" --- Variable | Description | Example --------- | ------ | ------ +-------- | ------ | `{{assignee}}` | The user that's assigned to the report. | `{{days_after_report(days)}}` | `{{details_custom_jira}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in a special Jira flavored markdown format. | From e32a62f7acab4f0a0d295675f34bc4616544be8c Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 12:53:51 +0200 Subject: [PATCH 06/15] Finish remaining variables --- docs/programs/integration-variables.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 57d8343e55b..fa858f3001f 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -7,24 +7,24 @@ id: "programs/integration-variables" Variable | Description | Example -------- | ------ | `{{assignee}}` | The user that's assigned to the report. | -`{{days_after_report(days)}}` | +`{{days_after_report(days)}}` | Provides a date based on the report creation date and the provided arugment on the provided argument. `{{days_after_report(5)}}` will output a date 5 days after the report was created. | `{{details_custom_jira}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in a special Jira flavored markdown format. | `{{details_markdown}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in markdown format. | `{{details_truncated}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format truncated at 4,000 characters. `{{details}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format. | -`{{due_date(days_from_now)}}` | +`{{due_date(days_from_now)}}` | Provides a date in the future based on the provided argument. `{{due_date(5)}}` will output a date 5 days from now. | `{{email_local_part}}` | The local part of the user creating the Jira issue. The local part of an email address is the part before the @ symbol. `{{email}}` | The email address of the user creating the Jira issue | `{{escalation_time}}` | The date and time of when the report was escalated to Jira. | -`{{jira_severity}}` | +`{{jira_severity}}` | The severity of the report in Jira mapping. `none` converts to `1` and `critical` converts to `5`. | `{{report_id}}` | The ID of the report | `{{report_link}}` | The url of the report | `{{reporter_link}}` | The url of the researcher's HackerOne profile | `{{reporter_name}}` | The name of the researcher that reported the vulnerability (this will fallback to the username if the researcher didn't provide their name) | `{{reporter_username}}` | The username of the researcher that reported the vulnerability | -`{{submission_date_custom_format}}` | -`{{submission_date_y_m_d}}` | -`{{submission_date}}` | The created date of the report | +`{{submission_date_custom_format}}` | The created date of the report in `DD-MM-YYYY` | +`{{submission_date_y_m_d}}` | The creation date of the report in `YYYY-MM-DD` | +`{{submission_date}}` | The created date of the report in `DD/MM/YYYY` | `{{title}}` | The title of the report | `{{vulnerability_information}}` | The description of the vulnerability in the report. | `{{weakness}}` | The CWE weakness of the report | From f6cbddcfd71991c460eb58b010711701df723210 Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 16:40:39 +0200 Subject: [PATCH 07/15] Update docs/programs/integration-variables.md Co-Authored-By: Saida --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index fa858f3001f..95ad396b356 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -7,7 +7,7 @@ id: "programs/integration-variables" Variable | Description | Example -------- | ------ | `{{assignee}}` | The user that's assigned to the report. | -`{{days_after_report(days)}}` | Provides a date based on the report creation date and the provided arugment on the provided argument. `{{days_after_report(5)}}` will output a date 5 days after the report was created. | +`{{days_after_report(days)}}` | Provides a date based on the report creation date and the provided argument. `{{days_after_report(5)}}` will output a date 5 days after the report was created. | `{{details_custom_jira}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in a special Jira flavored markdown format. | `{{details_markdown}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in markdown format. | `{{details_truncated}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format truncated at 4,000 characters. From 5ff8a24fd97e3203019fcf841bc2565a2813976b Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 16:40:50 +0200 Subject: [PATCH 08/15] Update docs/programs/integration-variables.md Co-Authored-By: Saida --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 95ad396b356..0fd715a78f1 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -8,7 +8,7 @@ Variable | Description | Example -------- | ------ | `{{assignee}}` | The user that's assigned to the report. | `{{days_after_report(days)}}` | Provides a date based on the report creation date and the provided argument. `{{days_after_report(5)}}` will output a date 5 days after the report was created. | -`{{details_custom_jira}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in a special Jira flavored markdown format. | +`{{details_custom_jira}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in a special Jira flavored markdown format. | `{{details_markdown}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in markdown format. | `{{details_truncated}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format truncated at 4,000 characters. `{{details}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format. | From a933befb7367545a79cb5ef9204a1ea6751a1b42 Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 16:41:00 +0200 Subject: [PATCH 09/15] Update docs/programs/integration-variables.md Co-Authored-By: Saida --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 0fd715a78f1..158075f5de7 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -9,7 +9,7 @@ Variable | Description | Example `{{assignee}}` | The user that's assigned to the report. | `{{days_after_report(days)}}` | Provides a date based on the report creation date and the provided argument. `{{days_after_report(5)}}` will output a date 5 days after the report was created. | `{{details_custom_jira}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in a special Jira flavored markdown format. | -`{{details_markdown}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in markdown format. | +`{{details_markdown}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in markdown format. | `{{details_truncated}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format truncated at 4,000 characters. `{{details}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format. | `{{due_date(days_from_now)}}` | Provides a date in the future based on the provided argument. `{{due_date(5)}}` will output a date 5 days from now. | From a18d0c49578f940db17b98e0b6765bae4e7c7deb Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 16:41:09 +0200 Subject: [PATCH 10/15] Update docs/programs/integration-variables.md Co-Authored-By: Saida --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 158075f5de7..533eee26727 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -10,7 +10,7 @@ Variable | Description | Example `{{days_after_report(days)}}` | Provides a date based on the report creation date and the provided argument. `{{days_after_report(5)}}` will output a date 5 days after the report was created. | `{{details_custom_jira}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in a special Jira flavored markdown format. | `{{details_markdown}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in markdown format. | -`{{details_truncated}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format truncated at 4,000 characters. +`{{details_truncated}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in plain text format truncated at 4,000 characters. `{{details}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format. | `{{due_date(days_from_now)}}` | Provides a date in the future based on the provided argument. `{{due_date(5)}}` will output a date 5 days from now. | `{{email_local_part}}` | The local part of the user creating the Jira issue. The local part of an email address is the part before the @ symbol. From 914c2c8edcef337ac1db6c5ac1115986faf4ca2e Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 16:41:20 +0200 Subject: [PATCH 11/15] Update docs/programs/integration-variables.md Co-Authored-By: Saida --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 533eee26727..8f4e5aaf38f 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -11,7 +11,7 @@ Variable | Description | Example `{{details_custom_jira}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in a special Jira flavored markdown format. | `{{details_markdown}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in markdown format. | `{{details_truncated}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in plain text format truncated at 4,000 characters. -`{{details}}` | The link, date, reporter, weaknesss, and description of the vulnerability in the report in plain text format. | +`{{details}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in plain text format. | `{{due_date(days_from_now)}}` | Provides a date in the future based on the provided argument. `{{due_date(5)}}` will output a date 5 days from now. | `{{email_local_part}}` | The local part of the user creating the Jira issue. The local part of an email address is the part before the @ symbol. `{{email}}` | The email address of the user creating the Jira issue | From 27ffaab90013680102f8624df9c4f3cfc50e964e Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 16:41:30 +0200 Subject: [PATCH 12/15] Update docs/programs/integration-variables.md Co-Authored-By: Saida --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 8f4e5aaf38f..34fbc7a6f1c 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -13,7 +13,7 @@ Variable | Description | Example `{{details_truncated}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in plain text format truncated at 4,000 characters. `{{details}}` | The link, date, reporter, weakness, and description of the vulnerability in the report in plain text format. | `{{due_date(days_from_now)}}` | Provides a date in the future based on the provided argument. `{{due_date(5)}}` will output a date 5 days from now. | -`{{email_local_part}}` | The local part of the user creating the Jira issue. The local part of an email address is the part before the @ symbol. +`{{email_local_part}}` | The local part of the email address of the user creating the Jira issue. The local part of an email address is the part before the @ symbol. `{{email}}` | The email address of the user creating the Jira issue | `{{escalation_time}}` | The date and time of when the report was escalated to Jira. | `{{jira_severity}}` | The severity of the report in Jira mapping. `none` converts to `1` and `critical` converts to `5`. | From 00d8732ff6e66027876e1abb56e266300b06d904 Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 16:41:38 +0200 Subject: [PATCH 13/15] Update docs/programs/integration-variables.md Co-Authored-By: Saida --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 34fbc7a6f1c..36315e2e284 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -18,7 +18,7 @@ Variable | Description | Example `{{escalation_time}}` | The date and time of when the report was escalated to Jira. | `{{jira_severity}}` | The severity of the report in Jira mapping. `none` converts to `1` and `critical` converts to `5`. | `{{report_id}}` | The ID of the report | -`{{report_link}}` | The url of the report | +`{{report_link}}` | The URL of the report | `{{reporter_link}}` | The url of the researcher's HackerOne profile | `{{reporter_name}}` | The name of the researcher that reported the vulnerability (this will fallback to the username if the researcher didn't provide their name) | `{{reporter_username}}` | The username of the researcher that reported the vulnerability | From 6277bd731594ca1a0a27c6fa93751733457bc2d2 Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 16:41:46 +0200 Subject: [PATCH 14/15] Update docs/programs/integration-variables.md Co-Authored-By: Saida --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 36315e2e284..08471370507 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -19,7 +19,7 @@ Variable | Description | Example `{{jira_severity}}` | The severity of the report in Jira mapping. `none` converts to `1` and `critical` converts to `5`. | `{{report_id}}` | The ID of the report | `{{report_link}}` | The URL of the report | -`{{reporter_link}}` | The url of the researcher's HackerOne profile | +`{{reporter_link}}` | The URL of the researcher's HackerOne profile | `{{reporter_name}}` | The name of the researcher that reported the vulnerability (this will fallback to the username if the researcher didn't provide their name) | `{{reporter_username}}` | The username of the researcher that reported the vulnerability | `{{submission_date_custom_format}}` | The created date of the report in `DD-MM-YYYY` | From 6de150969da601c388a7ba1cc5ef7e4a6956a4fc Mon Sep 17 00:00:00 2001 From: Martijn Russchen Date: Mon, 26 Aug 2019 16:42:23 +0200 Subject: [PATCH 15/15] Update docs/programs/integration-variables.md Co-Authored-By: Saida --- docs/programs/integration-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md index 08471370507..dbd7b001462 100644 --- a/docs/programs/integration-variables.md +++ b/docs/programs/integration-variables.md @@ -23,7 +23,7 @@ Variable | Description | Example `{{reporter_name}}` | The name of the researcher that reported the vulnerability (this will fallback to the username if the researcher didn't provide their name) | `{{reporter_username}}` | The username of the researcher that reported the vulnerability | `{{submission_date_custom_format}}` | The created date of the report in `DD-MM-YYYY` | -`{{submission_date_y_m_d}}` | The creation date of the report in `YYYY-MM-DD` | +`{{submission_date_y_m_d}}` | The created date of the report in `YYYY-MM-DD` | `{{submission_date}}` | The created date of the report in `DD/MM/YYYY` | `{{title}}` | The title of the report | `{{vulnerability_information}}` | The description of the vulnerability in the report. |