From 2c40e275268f4f2163d27e72482e58bead7597a0 Mon Sep 17 00:00:00 2001 From: Nakul Bharti Date: Thu, 10 Sep 2026 16:45:04 +0530 Subject: [PATCH 1/2] docs(jira): show what belongs inside the custom fields box The cloud setup step pointed at a whole nuclei config whose custom fields sit under a `custom_fields:` key, so users pasted that key into a box that supplies it for them and their fields landed one level too deep. Show the entries on their own with a warning, and correct the nuclei example to the `custom-fields` spelling the parser actually reads. Claude-Session: https://claude.ai/code/session_012yFBq5uTJ1VdtUKR32kZHQ Claude-Local-Session: claude --resume 509802c8-9204-430b-9d1d-49b8aca5b353 --- cloud/examples/connectjira.mdx | 21 +++++++++++++++++++-- opensource/nuclei/running.mdx | 2 +- 2 files changed, 20 insertions(+), 3 deletions(-) diff --git a/cloud/examples/connectjira.mdx b/cloud/examples/connectjira.mdx index 95ecc366..cdbfd246 100644 --- a/cloud/examples/connectjira.mdx +++ b/cloud/examples/connectjira.mdx @@ -117,8 +117,25 @@ Before getting started with this part of the setup ensure that you have complete - 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}}' + ``` + + + Do not include a `custom-fields:` line of your own. This box *is* the + custom-fields block, so adding that key nests your fields one level too + deep and the issue tracker cannot read them. The same applies to the + `custom_fields:` spelling. + + + - 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). diff --git a/opensource/nuclei/running.mdx b/opensource/nuclei/running.mdx index fc2f846b..5310f7e9 100644 --- a/opensource/nuclei/running.mdx +++ b/opensource/nuclei/running.mdx @@ -1131,7 +1131,7 @@ jira: # 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: From 9e1c49d0a840832c5780e9852f83925ed282a90f Mon Sep 17 00:00:00 2001 From: Nakul Bharti Date: Thu, 10 Sep 2026 20:28:08 +0530 Subject: [PATCH 2/2] docs(jira): say a pasted header is ignored, not that it breaks The aurora and platform-ui fixes lift such a key, so warning that the tracker cannot read the fields would be describing a failure that no longer happens. Claude-Session: https://claude.ai/code/session_012yFBq5uTJ1VdtUKR32kZHQ Claude-Local-Session: claude --resume 509802c8-9204-430b-9d1d-49b8aca5b353 --- cloud/examples/connectjira.mdx | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/cloud/examples/connectjira.mdx b/cloud/examples/connectjira.mdx index cdbfd246..04317f28 100644 --- a/cloud/examples/connectjira.mdx +++ b/cloud/examples/connectjira.mdx @@ -128,12 +128,11 @@ Before getting started with this part of the setup ensure that you have complete id: '{{if eq .Severity "critical"}}10104{{else}}4{{end}}' ``` - - Do not include a `custom-fields:` line of your own. This box *is* the - custom-fields block, so adding that key nests your fields one level too - deep and the issue tracker cannot read them. The same applies to the - `custom_fields:` spelling. - + + 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. + - 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).