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

Maintaining github connections with next-gen

We would like to set-up and start using a next-gen project. This involves migrating issues from an existing project that has been running for a number of years now. 

We've been creating git commits and pull requests using the JIRA issue IDs to link the two together and we don't want to lose this.

From what I understand, to move a project to next-gen we'd need to:

  1. Create a new next-gen project, which will have a new project ID
  2. Migrate the issues from the existing project to the next next-gen project, which will then update the ID with the new project ID

So what would happen to the existing links - will they break or is there a way of maintaining these?

Thanks

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 23, 2019

Hello Chris,

Doing some search in Atlassian documentation, there are no issues documented with the Bitbucket links (Branches) when migrating issues from classic project to Next-gen. In fact, the link works in the same way in both templates, so that should not give you any errors with the Classic to next-gen migration.

Doing a quick test in my Cloud instances, the issue was migrated just fine to the next-gen project and kept the branch link, although the Branch name is kept with the old issue key.

In the screenshot below, you can see the issue SCRUM-1 was correctly migrated to the Project NGP (Becoming NGP-1), however, the linked branch created before is still linked to the issue:

Screen Shot 2019-10-23 at 18.27.15.png

That being said, I can confirm that Bitbucket connections are kept after the movement with no issues, however, since we don't have any reported scenarios about this operation, I suggest you perform the steps below in case you still have any doubts about this change:

1 - Download a backup from your current JIRA instance

2 - Sign-up for a new Cloud site and connect it with a new bitbucket site

3 - Upload your instance backup and perform the migration in this test environment first, to  double-check that all were moved as you expected.

Let me know if this information helps.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events