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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Can auto linking of the Jira issues be prevented inside the Bitbucket pull request overview section?

When users create pull request, they will sometimes make addition comments about the request in the overview section. When they do, they are including related Jira issue numbers. When that happens, those issues will also show the pull request. However, it's only because of the Jira and Bitbucket auto-linking through the Jira issue number this happens. It becomes confusing looking at an issue linking to pull request which it has no real impact to. Is there a way to prevent this? Maybe with some special char characters around the Jira issue number?

1 answer

I figured out what is going on. It's not as I described after all. My users are committing changes on the same development branch (which is linked to a single issue) using different issues in the commit message. The pull request, regardless of the issue is displayed in the Summary title, is now seen in all issues that have commits on that branch. And when I look at the pull request's commit listing, it confirms this fact.

I just wish they wouldn't do this. I want them to use a single issue for branch/commits/pull requests. I just don't see a way to prevent the mixing of issues across the three objects.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events