Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Commit/Branch Linking Failure in Company-Managed Project

Kudo Taisei
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 28, 2025

We migrated the project from a Team-Managed to a Company-Managed project. After this migration, even when we create a branch using the user story key (e.g., `YA-1`) and make commits, they are not being associated with the corresponding user story.

We have confirmed that the settings and permissions are configured correctly. This association process worked without issues when the project was Team-Managed.

Additionally, the automation process that transitions the user story to "In Progress" after a commit (or branch creation) is functioning correctly. The only issue is that the commits themselves are not being linked to the user story.

I've reloaded it multiple times, but it's still not reflected.

1 answer

1 accepted

2 votes
Answer accepted
John Funk
Community Champion
April 28, 2025

HI Kudo - Welcome to the Atlassian Community!

When you move the issues from one project to another, the issue gets a new key. If the information in code repository was link to the issue in the TMP project, you need to link it to the new key in the CMP project. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events