Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
3
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
The Development panel currently shows the commits and branches related to the issue being displayed, through integration with Stash (and other VCSs). However, in an agile Git workflow, we create a branch for every story/bug/... and we solve subtasks in one or a few commits within that branch. As such, the parent issue usually displays 1 branch and a number of merge commits, and the subtasks display no branches (and of course the commits related to them).
I would suggest that the parent issue should display the branches related to it, and the commits related to itself + the commits related to its subtasks. The subtasks could display the branches related to themselves + the branches related to their parent, and only the commits related to themselves.
This way, while viewing a subtask you could get straight to the branch related to it even if that branch is linked to the parent issue, and while viewing the parent issue you would get a proper overview of the commits that have been done to resolve it even if those commits are linked to subtasks.
Also, while viewing a subtask you should not see commits related to the parent issue or sibling subtasks (unless they're also related to the subtask at hand, of course), since at that point you would expect a more specific/detailed view, and while viewing a parent issue you should not see branches of subtasks because you should view the subtasks themselves to get to their branches anyway.
Attachments
Issue Links
- relates to
-
JRACLOUD-39327 show commits related to subtasks of the issue being displayed
- Closed
-
JRASERVER-72848 Show commits related to linked issues of the issue being displayed
- Gathering Interest