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

Help! New issues are getting linked to ancient Bitbucket commits

We are using Jira Cloud and integrating with Bitbucket. We created a new project last month, and have made a bunch of issues. When we go to look at an issue, we see years-old commits from another project (which I think at one point may have had the same project key as our new project does). I can't see any way to remove them or to stop this from happening in future issues, short of removing the feature entirely and blinding me to actual current commits being done. I've tried changing the project key on the new project, to no avail.



1 answer

0 votes
Chris Buzon Community Leader Apr 12, 2021

Hey Matt!

There are two places I'd check first - one is your instance jira automation rules, and the other is post-functions on the workflow for the project in question.  For the workflow you'll need to go into the Edit mode on the active workflow, then check the transitions (especially the create event one) and see if anyone has connected something there.

If it's a jira automation rule you should see something in the ticket history, though if the rule was created a long time ago you may have to also check the webhooks for your jira instance -- 
That is found at the bottom of the "System" menu, in the advanced section. (above the one I am highlighting in this screenshot)


Thanks for your reply. Unfortunately, no joy.

Our "System Webhooks" are empty and I created the workflows myself - there is nothing funky there.

If you read the commits, it looks like it's referencing old tickets. So, we had a project for a long time, and then we created a new one for version 2.0 of it. We gave the 2.0 one the project key PTG (abbreviation of our app). The project for the 1.0 version has the key PRR, but I don't know if it always did.

Reading the commits and such that are getting falsely linked, I think what's happening is the 1.0 one maybe *used to* have the PTG key before I got here. I think when I create, say, PTG-123, it's linking to PRR-123 because it used to be PTG-123. The ticket names and commits look like things we'd reasonably expect to have seen in our app development at that time. 

Like Chris Buzon likes this

Suggest an answer

Log in or Sign up to answer
Site Admin

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