Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Migrating BitBucket issues to JIRA broke issue/commit links

I was quite saddened to discover that after migrating BitBucket issues to JIRA issues none of the "smart links" like issue #123 or commit SHA `deadbeefcafe...` seem to be there any more. I don't want to waste time re-associating everything issue we've ever created in the past 5 years, ug... any way to retroactively fix or do we just have to move on and let the old eventually fall off?

The commit history is full of messages like, `fix: don't use deprecated APIs (fixes #1234)` where 1234 was the BitBucket issue tracker issue ID. I expected the JIRA issue migration process to track the old BitBucket ID so that it could preserve this very useful feature (which, TBH, is table stakes because we're all so used to it from GitHub).

Similar to

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Jira admin's joining kit

Hello Atlassian's, This post will be a useful and valuable starter guide for new joiners into the team:

50 views 0 3
Read article

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