You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm relatively new to development tools like Bitbucket and GitHub and I'm not finding any solid answers in any documentation for this.
In one of my workflows in Jira, I have a trigger configured so that if a pull request is merged, the issue is transitioned to "Resolved" automatically. This is working great for our development team who is using GitHub.
That said - is it possible to link a single GitHub pull request to multiple Jira issues and execute that workflow trigger for all linked Jira issues? I believe you can do this via smart commits, but it would be more user-friendly for our users if all they had to do was include the issue key for each issue in the title or commit message.
EDIT: I should clarify - the developers are already including the multiple issue keys by copying/pasting the URLs to the issues in Jira in the commit message. Only the first issue key listed is transitioned successfully.
Has there been any official update to this?
@Alex Christensen I am also interested in linking a GitHub PR to multiple Jira Issues. Multiple smart commits have been made on a feature branch with the respective Jira issue key, and I would like a single PR for the branch to link to all of the Jira issues.
I have searched for a couple days and have not found a way to do this. The only way I could personally find would be to specify a custom issue key format for BitBucket to look for per the Using custom Jira issue keys with BitBucket Server article.
It does not state that you cannot add multiple keys so you may want to test on a dev instance. I'd be interested to know the results.
I'm also very interested in a solution for this.
In my case, I also have a trigger that "If a pull request is merged, the issue is transitioned to "Resolved" automatically, and we have succesfully linked all the Jira Issues to one Pull Request (all the Issues have the Pull Request number on their Development Section), but when the Pull request is merged, NONE of them transitions to Resolved :( We use GitHub.