Do not create a new issue in Jira if it is already opened #753
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Reopening this as it was closed by mistake. |
ehsandeep
added
the
Type: Enhancement
forgedhallpass
approved these changes
Sep 1, 2021
ehsandeep
added
the
Status: Completed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
** Description **
In the environment where the security and development teams are independent and share the same Jira ticketing server, it may happen, that the periodic scans discover the same set of issues every time. Instead of creating a new ticket every time, it is sufficient to just update the already opened one.
Proposed solution
I added a new boolean flag into the YAML configuration. If it is set to true, the existing jira ticket (if any) is updated. Otherwise, the behavior is the same as before.