Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I was just about to create my first feature branch with Git Flow. I want to attach the feature branch with a user story (although a story can have more than one feature).
So, this is a bit about how it can be confusing.
First there is a create branch in jira (on an issue, under the Development section, there is 'create branch') doing so gives a branch name "JIRA-12 User Feature"
Then, there is Gitflow. In SourceTree I say: GitFlow -> Create Feature Branch and it asks me for a branch name with the 'feature' prefix. So, it I will type it in: "feature/JIRA-12 User Feature"
But, you can't create a feature as a subtask of the User story. So, it's only tied to the Epic.
The only thing I can do is create a link.
This really isn't the question. Here's the question:
Should I use JIRA to do 'create branch' or should I use SourceTree to 'create feature branch'?
And, if I use SourceTree, how do I make sure that the 'link' is established (as it implies in the documentation)? Again, the documentation say "it can be done", but stops at the point of telling you how to do it.
Why is Atlassian so afraid to say: "Do it this way?". If someone disagrees, then they don't have to do it that way.
I don't know much about linking with Jira, but git flow is an optional git workflow. If it doesn't work with your personal/corporate workflow, don't use it. Creating a branch in SourceTree with the Branch button is only slightly more work.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.