Clarification about internal migration of my project to a new project template Edited

[ChuckieAJ]

Hi

I have followed the instructions and successfully migrated my issues from a classic template to a next-gen template. I have also moved the old template into trash.

I can see that the commits are still attached to the issues (which is great!). For example:

But:

• In the old project the key was MSASSIST.
• In the new project the key is MSA.

Now, I don't mind the change to a new key. And from now on I will prefix my source code commits with MSA instead. 

But, we still have all of those commits that moved over (and are correctly linked) to the issues that are now in my new project.

When I click on the Code option in the panel on the left, no data be being listed:

It does say it is correctly linked to bitbucket, but nothing is listed. I am assuming this is because it is wanting to list the MSA prefixed commits? I assumed it would list all the migrated issues commits here. But it doesn't.

# Update

I just did another commit (with the new MSA key) and as I expected it now shows information about the BitBucket repository:

Technically, it could have shown that anyway? Not to worry - it seems OK now.

[Earl McCutcheon · Accepted solution]

Hello @ChuckieAJ ,

Thanks for posting the update noting the solution you found, It will help others out if anyone else runs int to this looking for a solution. 

I just wanted to double-check if you are all good or if you any follow-up questions.

Regards,
Earl

[ChuckieAJ]

Hi @Earl McCutcheon 

I think I am OK with this now.

Thanks!