Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Git-flow not 100% compatible from 2.7.1 and above


This is not a duplicate from

I've done the `getopt` thing and git flow started working but 100% as before.

In my case, I usually review my team work by checking the `features` from one dev or another. So I have git-flow initialised like this:

feature = feature/
release = release/
hotfix = hotfix/
support = support/
versiontag =

So, when checking another dev jobs I go to `feature/ic/CODE-000` and do the usual flow actions like finishing the feature or the hotfix.

From 2.7.1 and above (I tried with v3 as well) having that config results in git flow not recognizing branches like `feature/*/CODE-000` as a feature, so when performing flow the next action always gives me the primary options, like "Start a new feature" and not "Finish feature".

If I config the features to be like `feature/ic/` then git flow recognizes them as they should. The problem is that I need to be able to go through `feature/ic` or `feature/ns` or `feature/jf` without the need of changing the config every time.

Hope someone can help me.

1 answer

0 votes
Manju Atlassian Team Nov 07, 2018

We are aware of some issues with respect to gitflow since we upgraded to gitflow avh and actively working to get to the root of it and resolve them. We request you to submit a ticket on for us to get to know all related issues and fix them for you. Thanks for your patience and we really appreciate the understanding in the meanwhile. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events