docs(jira): show what belongs inside the custom fields box

cloud/examples/connectjira.mdx

@@ -1,42 +1,42 @@
 ---
 title: "Create Tickets for Jira"
 description: "Create actionable follow up for exploitable vulnerabilities in Jira"
 sidebarTitle: "Create Tickets for Jira"
 ---
 
 ## Summary
 ProjectDiscovery Cloud Platform has provided you with comprehensive scan results on exploitable vulnerabilities - what's next? You want to get your team involved and have a more seamless pipeline between data visibility, discovery, and follow up. 
 For your organization this means getting important tasks into Jira!
 
 
 In this example, we'll walk through setting up this important workflow for a brand new user. You will add assets, configure a Jira integration, and initiate a scan to create a ticket for your team to take action. 
 
 ### What You'll Do 
 In this walkthrough we're going to go step-by-step to complete the following actions:
 
 - Add Assets 
 - Configure Jira
 - Configure ProjectDiscovery Cloud Platform for Jira ticketing
 - Start a scan to test your new integration
 
 ### Prerequisites 
 To complete the integration you will need to have the correct permissions to access account details within Jira. Refer to [Atlassian's documentation](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) for additional details.
 
 <Note>If you are not a Jira administrator you may need your organization's Jira administrator for assistance in collecting these details. </Note>
 
 **You will need the following:**
 
 - Jira instance URL
 - Jira Account ID
 - Jira email
 - Jira API Token
 - Jira Project name
 
 ## Add Assets
 
 For this example we're going to stick with the simplest path and add assets to your PDCP environment by uploading a .TXT file with the domains you want to include for scanning. 
 
 If you already have assets in ProjectDiscovery Cloud Platform, you can skip ahead to Connecting Slack. For for other Asset upload options check out the docs on [Adding Assets.](/cloud/assets/adding-assets)
 
 
 <Steps>
@@ -58,26 +58,26 @@
 
 </Steps>
 
 Once your assets, you will need to connect your ProjectDiscovery Cloud Platform to your Jira account.
 
 If you have questions on Assets - check out the [Assets - FAQ](/cloud/assets/overview#faq). 
 
 ## Connecting Jira
 After adding your assets, you will need to connect your ProjectDiscovery Cloud Platform environment to Jira. There are two parts to this, the part you will need to complete in your Jira environment and the details you'll need to add to ProjectDiscovery Cloud Platform. 
 
 ### Jira Setup
 
 Logged in to Jira as an administrator visit [this link]( https://id.atlassian.com/manage-profile/products) to locate your Jira instance URL.
 You can also [use the REST API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/) to obtain these details. 
 
 *Note: The format for URLs in Jira will vary depending on your account type (Jira Cloud vs on-prem)*
 
 <Steps>
   <Step title="Find your Jira instance URL">
   Log in to your Jira account and locate the following information:
   - Jira instance URL
   - Jira Account ID
   - Jira Project Name
 
   *Note: To locate your Jira instant URL -  Click your Profile menu in the upper-right, then select **Profile**. In the URL after /people/ is your account ID.*
 
@@ -93,21 +93,21 @@
   </Step>
 </Steps>
 
 Next up, you will be adding these details from Jira to your environment in ProjectDiscovery Cloud Platform!
 
 ### ProjectDiscovery Cloud Platform Setup 
 Before getting started with this part of the setup ensure that you have completed the configuration required in Jira.
 
 <Steps>
   <Step title="Launch the Jira integration in PDCP">
   Navigate to **Scans → Configurations** and under Ticketing select Connect under the option for Jira. 
   </Step>
   <Step title="Add your config details">
   In PDCP complete the information for Jira including: 
   - A name for your Jira Configuration
   - Jira instance URL
   - Jira account ID
   - Jira Email
   - Jira API Token
   - *(Optional) Select Enable for all scans option if desired (you can also select this option during scan creation)*
   - Select **Next** to continue the Jira integration setup. 
@@ -117,20 +117,36 @@
   - Provide the **Jira Issue type** you want to have created. 
   - Add the Closed status. (Default is "Done" but this field can be edited)
   - Choose your preferred options (toggle) for **Severity** and **Deduplication**. 
-  - Add any Custom field details you want to include.
-     - Refer to [an example on custom fields from ProjectDiscovery](/opensource/nuclei/running#nuclei-reporting) (*scroll to Jira*)
+  - Add any Custom field details you want to include. Enter one entry per field, each mapping `id`, `name` or `freeform` to a value:
+
+    ```yaml
+    customfield_00001:
+      name: 'Nuclei'
+    customfield_00002:
+      freeform: '{{.CVSSMetrics}}'
+    priority:
+      id: '{{if eq .Severity "critical"}}10104{{else}}4{{end}}'
+    ```
+
+    <Note>
+      This box is the custom-fields block, so your entries go in directly. If you
+      paste an example that still has a `custom-fields:` (or `custom_fields:`)
+      line at the top, that line is ignored and the fields under it are used.
+    </Note>
+
+     - Use `id` or `name` for dropdown fields, and `freeform` for text fields.
      - Review Atlassian's documentation on [creating custom fields](https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/), or [locating existing custom field IDs](https://confluence.atlassian.com/jirakb/how-to-find-any-custom-field-s-ids-744522503.html).
   </Step>
   <Step title="Finalize your configuration for Jira">
   Once you're satisfied with your configuration select **Verify** to complete your Jira integration.
   </Step>
 </Steps>
 
 Now that your configuration is set up, you can create a scan and verify your Jira integration. 
 
 ## Create a Scan 
 
 The final step is to create a scan, verify that your Jira integration is set up correctly, and check for the corresponding ticket in the Jira project you configured. 
 
 <Steps>
   <Step title="Create a new scan">
@@ -153,7 +169,7 @@
 </Steps>
 
 ## What's Next? 
 This example focuses on the process of integrating with Jira to create tickets for your team based on scan results. 
 
 ProjectDiscovery Cloud Platform also supports workflows for alerting for Slack, MS Teams, Email and custom webhooks. 
 

opensource/nuclei/running.mdx

@@ -16,7 +16,7 @@
 
 For automation in pipelines, see [Running Nuclei in CI/CD](/opensource/nuclei/ci-cd).
 
 Nuclei supports various input formats to run template against, including urls, hosts, ips, cidrs, asn, openapi, swagger, proxify, burpsuite exported data and more. To learn more on using input specify options, you can refer [nuclei input formats](/opensource/nuclei/input-formats).
 
 These inputs can be given to nuclei using `-l` and `-input-mode` flags.
 
@@ -25,13 +25,13 @@
   -im, -input-mode string       mode of input file (list, burp, jsonl, yaml, openapi, swagger) (default "list")
 ```
 
   Executing nuclei against a list of inputs (urls, hosts, ips, cidrs, asn) is as simple as running the following command:
 
 ```bash
   nuclei -l targets.txt
 ```
 
   For running other input formats (burp, jsonl, yaml, openapi, swagger), you can use the `-im` flag to specify the input mode.
 
 ```bash
   nuclei -l targets.burp -im burp
@@ -226,7 +226,7 @@
   <Accordion title="For GitLab Project" icon="pencil">
     ```bash
     export GITLAB_SERVER_URL=https://gitlab.com
     # The GitLab token must have the read_api and read_repository scope
     export GITLAB_TOKEN=XXXXXXXXXX
     # Comma separated list of repository IDs (not names)
     export GITLAB_REPOSITORY_IDS=12345,67890
@@ -719,11 +719,11 @@
 
 <Warning>
   Do not modify the active **.nuclei-ignore** file. Nuclei can replace it during
   a template update. To override the denylist, use [Nuclei
   configuration](/opensource/nuclei/running#nuclei-config) or the include flags.
 </Warning>
 
 To prioritize certain templates or tags over the [.nuclei-ignore](https://github.com/projectdiscovery/nuclei-templates/blob/master/.nuclei-ignore) file or denylist, you must use the `-include-templates` or `-include-tags` flags. This will ensure that the specified templates or tags take precedence over any `.nuclei-ignore` or denylist entries.
 
 <Note>
 Example of running blocked templates
@@ -735,9 +735,9 @@
 </Note>
 
 <Note>
 Example of executing a specific template that is in the denylist
 
 Say that you have custom templates globbed (`*`) in the denylist on the Nuclei configuration file.
 
 ```yaml
 # ...
@@ -766,7 +766,7 @@
 
 ### Scan on internet database
 
 Nuclei supports integration with [uncover module](https://github.com/projectdiscovery/uncover) that supports services like Shodan, Censys, Hunter, Zoomeye, many more to execute Nuclei on these databases.
 
 Here are uncover options to use -
 
@@ -852,7 +852,7 @@
 
 ### Template profiles
 
 The `profile` setting accepts a file path or an extensionless community profile ID. For a relative YAML file path, Nuclei checks the current directory first and then `profiles/` in the active template root. For a profile ID, it searches that profile directory and its subdirectories for a matching YAML file.
 
 A profile can provide targets through a multiline `targets-inline` value. A multiline `list` value also becomes inline targets, while a single-line `list` value remains a file path. Nuclei trims each target and ignores blank lines and lines that start with `#`.
 
@@ -860,14 +860,14 @@
 
 ### Storage locations
 
 Nuclei keeps configuration, installed data, persistent state, and regenerable cache in separate directories:
 
 | Purpose | Default location |
 | --- | --- |
 | User configuration | `$XDG_CONFIG_HOME/nuclei` |
 | Public template installation target | `$XDG_DATA_HOME/nuclei/nuclei-templates` |
 | Restart-persistent state | `$XDG_STATE_HOME/nuclei` |
 | Regenerable cache | `$XDG_CACHE_HOME/nuclei` |
 
 `NUCLEI_CONFIG_DIR` remains a compatibility override for the user configuration directory, including `config.yaml`, signing keys, and reporting configuration. It does not change the XDG data, state, or cache locations.
 
@@ -1017,9 +1017,9 @@
 
 ## Nuclei Reporting
 
 Nuclei comes with reporting module support with the release of v2.3.0 supporting GitHub, GitLab, and Jira integration, this allows nuclei engine to create automatic tickets on the supported platform based on found results.
 
 | Platform    | GitHub | GitLab | Jira | Markdown | SARIF | Elasticsearch | Splunk HEC | MongoDB |
 |-------------|:------:|:------:|:----:|:--------:|:-----:|:-------------:|:----------:|:-------:|
 | Support     |   ✔    |   ✔    |  ✔   |    ✔     |   ✔   |       ✔       |     ✔      |     ✔   |
 
@@ -1068,7 +1068,7 @@
   index-name: nuclei
 ```
 
 To forward results to Splunk HEC, create a config file with the following content and replace the appropriate values:
 
 ```yaml
 # splunkhec contains configuration options for splunkhec exporter
@@ -1087,19 +1087,19 @@
   token: '$hec_token'
 ```
 
 To forward results to Jira, create a config file with the following content and replace the appropriate values:
 
 The Jira reporting options allows for custom fields, as well as using variables from the Nuclei templates in those custom fields.
 The supported variables currently are: `$CVSSMetrics`, `$CVEID`, `$CWEID`, `$Host`, `$Severity`, `$CVSSScore`, `$Name`
 
 In addition, Jira is strict when it comes to custom field entry. If the field is a dropdown, Jira accepts only the case sensitive specific string and the API call is slightly different. To support this, there are three types of customfields.
 
 - `name` is the dropdown value
 - `id` is the ID value of the dropdown
 - `freeform` is if the customfield the entry of any value
 
 To avoid duplication, the JQL query run can be slightly modified by the config file.
 The `CLOSED_STATUS` can be changed in the Jira template file using the `status-not` variable.
 `summary ~ TEMPLATE_NAME AND summary ~ HOSTNAME AND status != CLOSED_STATUS`
 
 ```yaml
@@ -1131,7 +1131,7 @@
   # freeform can be used if the custom field is just a text entry
   # Variables can be used to pull various pieces of data from the finding itself.
   # Supported variables: $CVSSMetrics, $CVEID, $CWEID, $Host, $Severity, $CVSSScore, $Name
-  custom_fields:
+  custom-fields:
     customfield_00001:
       name: 'Nuclei'
     customfield_00002: