Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Invalid Pull Request are being associated and raising the counts under development panel of an issue Edited

Invalid Pull Request are being associated and raising the counts under development panel of an issue.
We are using Bitbucket Server and that is connected with our Jira.
We are following the below standards to have a correct count advice in devlopment panel for an jira issue.

Pull requests Bitbucket,

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 in the pull request title.
Ensure that the source branch name includes the issue key.
If you create the pull request from the Branches dialog of the Development panel in a Jira issue, the issue key is added automatically.

For example, if you create a pull request that has "TIS-3" in the title, the TIS-3 issue will automatically transition from 'In Progress' to 'In Review'. If you reopen, decline, or merge the pull request, it will also transition the TIS-3 issue accordingly.


Pull requests are linked automatically if the issue key is included in the pull request's title or in the source branch name.
We do not understand why it is linking/associating and raising the counts of the pull request that are not part.
We dont understand if it picks up the issues from the description as well ?




Looking at the history of that merge request, it seems like the initial changes included a bunch of unrelated commits, some of which may have included unrelated references. The history was corrected, but unfortunately it looks like the link/count/associations was not. Are these links on dev pannel re-scanned when these things change ?

0 answers

Suggest an answer

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

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

260 views 7 7
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