How to declare the exact resources IDs that should be associated with the deployment on the receiver side? #90
Description
In our work process a feature might contains several PRs.
When I'm doing a staging deployment, I would like to forward the information which actual Jira tickets should be associated with the deployment, the rest should be not:
Let's say I have commit messages containing JIRA-1, JIRA-2, JIRA-3.
Only JIRA-2 is considered to be completed around this time (the rest will still have some upcoming PRs, they are still in progress) and somehow I would like to forward this information (I have all the info during github actions to compute this information).
Is there any possibility to override Jira's functionality which reads and parses all commit messages and then all the collected Jira IDs will be associated with the deployment object?