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

Github branches linked to multiple issues

I have created an issue in my Kanban board. This issue has multiple subtasks. Is there a way in my development task to associate all the subtask to the parent issue Git branch? 

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer Atlassian Team Apr 29, 2021

Hi Jerry,

If I understand the concern here, you are wanting to be able to see this specific Git branch across all the subtasks when looking at each individual issue. 

Unfortunately, this is not something that you can do based off of just a single parent issue in Jira.  When it comes to displaying a branch in the development panel in Jira, only the title of that branch is searched for issuekeys to determine which issues this appears on.  However I was able to test this against a branch name having 2 distinct issuekeys.  In my testing when the branch name contains multiple issuekeys, that branch does display on each issue.  This probably is not feasible though for issues with lots of subtasks, or in cases when subtasks in Jira are created after the branch is created as renaming a branch is not always a trivial task in git.

The way the Smart Commits feature in Jira works is based on where Jira can see specific issue keys. This is commonly something you can more easily expand on in commit messages or pull request messages where you can enter in several Jira issue keys, but in the case of branches, we only have the name of the branch itself to associate with specific Jira issues. 

If all the subtasks in Jira were already created, and the branch had not yet been made, then it might be possible to do what you are looking for here, albeit a potentially large branch name will have to be used to include each issuekey in question.  Otherwise I don't really see a feasible way to do what I think you are wanting to see here.  Perhaps leveraging a commit or pull request in either the title or message can still serve to help Jira users see where the code that relates to this issue is being changed.

Does this help?

Andy

thank you... not want I wanted to hear... but yes, it makes senses.

 

Jerry   

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

244 views 2 1
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