Add Jira issues inputs in addition to product releases #151
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.
This will allow automated processing of Jira tickets based on specific JQL search query (thought there is currently no useful prerequisite to process the issues).
Additionally, it is possible to implement custom input classes.
Example rule:
This change also simplifies managing issues using a unique label: ReTaSC will fetch the unique issue by single identifying label from Jira for each prerequisite. This means there are multiple Jira API queries, but it is much easier to understand then fetching a group of issues using a common label.