Default state presented not equal to actual state (AST-115349)

[cx-rahul-pidde]

By submitting a PR to this repository, you agree to the terms within the Checkmarx Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.

Description

Fixed bugs related to SAST custom states

References

Default state presented not equal to actual state
Admin cannot update result to a Custom state

Testing

Case 1-

• Select any vulnerability and update the state (any).
  Expected - the tree wll be restored with latest state by group by
• Close VSCode and select same vulnerability.
  Expected - the tree wll be restored with latest updated state by group by

Case 2-

• Select any vulnerability and update severity (any)
  Expected - the tree wll be restored with latest severity by group by
• Close VSCode and select same vulnerability.
  Expected - the tree wll be restored with latest updated severity by group by

Note - Try multiple times updating states and severity.

Checklist

• I have added documentation for new/changed functionality in this PR (if applicable).
• All active GitHub checks for tests, formatting, and security are passing
• The correct base branch is being used

[github-actions]

Checkmarx One – Scan Summary & Details – 223fb720-9da1-4cd4-abda-beef484f2e83

Great job! No new security vulnerabilities introduced in this pull request

[cx-anurag-dalke]

ok