[JIRA] (JENKINS-59621) Support SLUG/ID Syntax for Jira Tickets

[richardsimpson@outlook.com (JIRA)]

Richard Simpson created an issue

Jenkins / JENKINS-59621 Support SLUG/ID Syntax for Jira Tickets Issue Type: New Feature Assignee: Rafal Myslek Components: atlassian-jira-software-cloud-plugin Created: 2019-10-02 03:44 Priority: Minor Reporter: Richard Simpson For our company, we use the branch syntax `TEST/123_Some_Description` for our branches, with the branch corresponding to the the ticket `TEST-123`. This allows use to take advantage of many git clients behaviors of grouping related branches. It'd be nice if this was supported. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[tpechacek@atlassian.com (JIRA)]

Taylor Pechacek commented on JENKINS-59621

Re: Support SLUG/ID Syntax for Jira Tickets Hey Richard Simpson 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

Add Comment

[richardsimpson@outlook.com (JIRA)]

Richard Simpson updated an issue

Jenkins / JENKINS-59621

Support SLUG/ID Syntax for Jira Tickets

Change By: Richard Simpson Attachment: image-2019-11-12-19-54-10-450.png

Add Comment

[richardsimpson@outlook.com (JIRA)]

Richard Simpson commented on JENKINS-59621

Re: Support SLUG/ID Syntax for Jira Tickets Taylor Pechacek 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`

Add Comment