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’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs