Fix Version behavior inconsistent for parent and child versions in version hierarchy

We're seeing inconsistent behavior where sometimes you specify a child version value for Fix Version and the parent version gets automatically added and other times parent version doesn't get added. How can I force the behavior to be consistent and hopefully always add the parent version?

We have single level version hierarchy. For example, major version is parent and there's several child versions, one for each development iteration. We do a releasable build at end of each iteration so every issue inclued for an iteration will have a child version specified. We'd like for every closed issue to have both it's child and parent version populated in Fix Version field.

We have "Version Synchronizer" enabled but I'm not sure what it does.

2 answers

Does the Synchronize from GH shows any issues which are not having parent versions?

I get the message, "All Versions are synchronised." when I do Synchronise from GH Tools menu. But there's still issues that don't show both major version and milestone in Fix Version field.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

203 views 0 5
Read article

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