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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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,462,021
Community Members
 
Community Events
176
Community Groups

Commits are confused becaus Jira projects with the same name from two instances point to Bitbucket

Edited

We recently migrated from one Jira instance to another.  The issues in the new instance are showing commits from the old project - even after we rekeyed the project.

Here's the setup:

Jira instance 1, project BI - links to bitbucket

Jira instance 2, project BI - now also links to Bitbucket

If I create an issue in Jira2, BI-430 for example, the commit that was from JIRA2, BI-430 is showing.

We've tried to rename the BI project in Jira2, but it still references the oldkey in Bitbucket.

How do we remedy this?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events