Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: restore previous priorityIsSeverity value after retry #197

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

rback123
Copy link

  • Tests written and linted ℹ︎
  • Documentation written ℹ︎
  • Commit history is tidy ℹ︎

What this does

Explain why this PR exists

This PR fixes an issue where the priorityIsSeverity value is modified for a retry attempt but is never restored to the previous value after the retry. Without this fix, any subsequent vulnForJira processed (for loop on line 249) may have an incorrect Jira priority value.

Notes for the reviewer

Replicate by this scenario:

  1. Use --priorityIsSeverity=true
  2. Attempt to create multiple Jira tickets of varying priority
  3. Experience an error during Jira creation
    1. Example - the Snyk severity maps to a Jira priority that doesn't exist
  4. Check priority of tickets processed and created after the error is encountered

More information

  • n/a

Screenshots

  • n/a

lili2311 and others added 5 commits December 2, 2022 18:35
Added the optional flag for the due date built-in flag.
Updated README with instructions

Co-authored-by: Alexandre Vallières-Lagacé <[email protected]>
…vices#192)

Switch from:
- `snyk.io/api` to `api.snyk.io`
- `api.snyk.io/api` to `api.snyk.io`
- `snyk.io/vuln` to `security.snyk.io/vuln`
- `api.snyk.io/v3` to `api.snyk.io/rest`
@aarlaud
Copy link
Contributor

aarlaud commented Oct 29, 2024

horribly behind, apologies. please rebase off develop to get this in. thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants