Hi! I have been taking a look at how Jira assigns issues as deployed today. Form my reading it seems that for a deployment to be linked to a Jira issue, the commit associated with the deploy must reference the issue key in it’s commit message.
A deployment to an environment, such as production or testing, is linked if a commit associated with the deploy contains the issue key in its commit message. The issue key must be included in the commit to activate this feature [1].
However I have a web app that I tend to deploy several features + bug fixes at once to production. We name our merge requests the name of the Jira issue. This means that the Jira board shows that only 1 (the last request to be merged in) of the Jira issues have been deployed to production.
This is fairly standard deployment CI/CD behaviour, so hoping a solution exists? Thanks!
