Hacker0x01 · martijnrusschen · Aug 26, 2019 · Aug 20, 2019 · Aug 20, 2019 · Aug 20, 2019
diff --git a/docs/programs/integration-variables.md b/docs/programs/integration-variables.md
@@ -0,0 +1,30 @@
+---
+title: "Integration Variables"
+path: "/programs/integration-variables.html"
+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 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, 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 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`. |
+`{{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}}` | The created date of the report in `DD-MM-YYYY` |
+`{{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. |
+`{{weakness}}` | The CWE weakness of the report |
diff --git a/docs/programs/jira-faqs.md b/docs/programs/jira-faqs.md
@@ -8,5 +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.<br><br>To integrate Jira with multiple HackerOne programs:<ul>1. Follow all of the [Jira Server steps](jira-server-integration.html) for the first program you want to integrate.</ul><ul>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).<ul><li>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.</li></ul></ul>
-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.<br><br>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.<br><br>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.
diff --git 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