Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,293,211
Community Members
 
Community Events
165
Community Groups

How do I link a merged-in PR to a Jira ?

Edited

Hi all,

I'm new to Atlassian/Bitbucket/Jira, we use it at work and I'm loving it so far.

I now know that I should embed the Jira number in the branch name or PR title or commit description to link the two together but is there a way to do this for an older PR?

Basically, I had a Jira ticket "x", I had a PR "y" consisting of commit "z". I have already merged in "y", and didn't use "x" anywhere in the title of "y" or "z". Is there still a way to link these together?

 

Much thanks,

Agam

 

2 answers

2 accepted

3 votes
Answer accepted

We have this issue sometimes - we simply edit the title of the merged PR to add the Jira issue(s) ID. That works well!

Works like a charm, thanks!

How do you edit the PR title after merged?, I'm unable to do it 

Hmm, might be a setting on your GitHub repo or org? On the PR's in my main repo, I see an "Edit" button next to the PR title - clicking it lets me edit the PR's title and description.

Yes this works great, thanks!

Ends up this is also in official docs:

Pull requests

Do at least one of the following:

- Include a commit in the pull request that has the issue key in the commit message. Note, the commit cannot be a merge commit.

- Include the issue key at the beginning of the pull request title.

- Ensure that the source branch name also includes the issue key at the beginning of the branch name.

0 votes
Answer accepted
Mikael Sandberg Community Leader Mar 13, 2018

Once you have merged a PR the only thing you can do is add the issue key as a comment in the PR, that will give you sort of a link where it allows you to click on the key and see the info from Jira, but it will not show the PR as related to the issue in Jira. You could revert the merge, recreate your change/s on a new branch and then created a new PR if you want. You cannot use the same branch for the new PR.

Reverting a regular commit just effectively undoes what that commit did, and is fairly straightforward. But reverting a merge commit also undoes the _data_ that the commit changed, but it does absolutely nothing to the effects on _history_ that the merge had.

So the merge will still exist, and it will still be seen as joining the two branches together, and future merges will see that merge as the last shared state - and the revert that reverted the merge brought in will not affect that at all.

So a "revert" undoes the data changes, but it's very much _not_ an "undo" in the sense that it doesn't undo the effects of a commit on the repository history.

So if you think of "revert" as "undo", then you're going to always miss this part of reverts. Yes, it undoes the data, but no, it doesn't undo history.

- Linus Torvalds

Thanks for the reply, I thought as much. Just adding the link works for now.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you