From a81cefee6b91804b2f990d9f7baafd50e941f3d3 Mon Sep 17 00:00:00 2001 From: Mike Romard Date: Mon, 6 Jan 2025 13:42:59 +0000 Subject: [PATCH] GITBOOK-8656: MR - update jira-tickets-for-new-vulns --- .../snyk-tools/tool-jira-tickets-for-new-vulns.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/scan-with-snyk/snyk-tools/tool-jira-tickets-for-new-vulns.md b/docs/scan-with-snyk/snyk-tools/tool-jira-tickets-for-new-vulns.md index b6709554d6c5..39c3832ddb0e 100644 --- a/docs/scan-with-snyk/snyk-tools/tool-jira-tickets-for-new-vulns.md +++ b/docs/scan-with-snyk/snyk-tools/tool-jira-tickets-for-new-vulns.md @@ -12,9 +12,9 @@ Use the binaries from [the release page](https://github.com/snyk-tech-services/j ``` ./snyk-jira-sync- - -orgID= // Can find it under settings - -token= // Snyk API Token. Service accounts work. - -jiraProjectKey= // Jira project Key the tickets will be opened against + --orgID= // Can find it under settings + --token= // Snyk API Token. Service accounts work. + --jiraProjectKey= // Jira project Key the tickets will be opened against ``` **Extended options** @@ -132,7 +132,7 @@ jira: assigneeId: 123abc456def789 assigneeName: AccountName priorityIsSeverity: true # - label: label1 # , + labels: label1 # , jiraProjectKey: testProject priorityIsSeverity: false # (defaults: Low|Medium|High|Critical=>Low|Medium|High|Highest) customMandatoryFields: @@ -143,6 +143,6 @@ jira: **Notes:** * The token is not expected to be present in the config file. -* Command line arguments override the config file. Example: Using the config file above, running `./snyk-jira-sync-macOs -Org=1234 -configFile=true -token=123` the org ID used by the tool will be 1234 and not a1b2c3de-99b1-4f3f-bfdb-6ee4b4990513. +* Command line arguments override the config file. Example: Using the config file above, running `./snyk-jira-sync-macOs --Org=1234 --configFile=./path/to/folder --token=123` the org ID used by the tool will be 1234 and not a1b2c3de-99b1-4f3f-bfdb-6ee4b4990513. * See 'Extended options' for default values. * Ensure you use the same issue type that is configured in your Jira. Default is Bug. Verify the type is use (or default) exists in your Jira configuration.