• Community
  • Products
  • Jira
  • Questions
  • Jira + Bitbucket + SourceTree + gitflow - how to use sourcetree's gitflow features while creating branches in JIRA?

Jira + Bitbucket + SourceTree + gitflow - how to use sourcetree's gitflow features while creating branches in JIRA?

In SourceTree, I can use the gitflow button to start/complete features, hotfixes, etc. and it will automatically handle a lot of the gitflow details (and is well organized). However, this creates local branches and does not link them to JIRA issues.

In JIRA, I can create a branch from an issue. This branch is remote (in Bitbucket) and so there is no clear way to use the nice gitflow features of SourceTree.

How can I use both JIRA-initiated and tracked branches with the gitflow features of SourceTree?

8 answers

I am new to all these tools and also git. I have only figured out 2 ways, neither particularly clean, intuitive, or satisfying, so I am hoping an expert can help me.

The first way is to create the branch in JIRA but don't check out from Bitbucket, then in SourceTree use gitflow button to create a new feature and change the source from the default to the new remote branch. The annoyance with this is that you have to remember to manually change the repos that pushes go to, every time, to the remote branch (and easy to make a mistake).

The second way is to create the issue branch in JIRA, checkout from bitbucket (which creates a local copy of the remote branch), and then use SourceTree gitflow to create feature/bugfix branches from this issue branch. The problem is that now you have a pointless intermediate branch that makes it harder to push your updates through the chain.

I would also love to see an answer to this...

SourceTree's gitflow feature look like very useful.

But in our Bitbucket - each branch has permissions and any changes should  be passed to branch via pull requests. So in this way - we can not use SourceTree gitflow features (because we need pull requests instead of merges)

It would be great if:

  • "Finish feature" button - create pull request instead of local merge
  • "Finish hotfix" button - create pull request to master and develop branches instead of local merges.
  • etc.

+1 

  • "Finish feature" button - create pull request instead of local merge
  • "Finish hitfix" button -create pull request to master and develop branches instead of local merges.
  • "Finish feature" button - create pull request instead of local merge
  • "Finish hitfix" button -create pull request to master and develop branches instead of local merges.

+1

+1 "Finish feature" must be create pull request. Otherwise, the "finish feature" is meaningless.

I have no idea why so did SourceTree

+1

  • "Finish feature" button - create pull request instead of local merge
  • "Finish hitfix" button -create pull request to master and develop branches instead of local merges.

I am new to Jira/Git/Bit/SourceTree world but I believe this is a great question and addition to sourceTree

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,337 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot