Hey richicoder I would love to know more about what you mean by 'git clients behaviours of grouping related branches'.

• Why are you grouping related branches together - for what purpose? How does this tie into your CI/CD workflows?
• How is this pattern being used in practice - can you describe the actual workflow?

Just trying to gain a bit more context for this ask before we look at adding this capability.

The standard syntax even for Git + Jira has always been the "{Project_Key}-{Issue_ID}" pattern, which is what we primarily look for to tie this information to the Jira issue.

Therefore, if we update the syntax support to include this, we may want to add it in other tools as well. 

Thanks in advance!

Taylor Pechacek, Jira Cloud PM

tpechacek

In short, a number of git GUI clients like GitKraken and SourceTree will interpret forward slashes in branch names as folders and present a folder-like tree structure. This allows a simple way to group branches for which we've established the convention of doing "{Project_Key}/{Issue_ID}_<Brief Description>" for `git branch` names. With each of our teams having their own projects, this allow us to focus on just our teams branches pretty easily. This is mostly a convenience and naming convention and otherwise don't affect our normal flows.

UI Example:

corresponds to `feature/offline-static`