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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

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

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
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

887 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