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?
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.