How to manage multiple release versions in development at the same time for same product? Edited

We want to release a version "1.1" in 2 months.

Feature X is huge (architectural change with dependancies). Feature Y and Z are manageable.

Team is working on Feature X now, but know it won't be feature complete for awhile. 

Is it better to:

A) Flag tickets as 1.1 fix version and drop them in the sprints? or

B) Work off two fix versions in parallel?

Goal is to be able to report what features will make the 1.1 release but also show that work is being done on other long term feature.

1 answer

We use JIRA 7.10 server version.

If you are committing code for Feature X in the same code base as for the release which will contain the 'manageable' Features Y and Z, then the work for Features X/Y/Z should be against the same FixVersion.

Even if you are not going to announce Feature X (when you announce Feature Y and Z), the software contains (hidden or alpha-/beta-feature) Feature X's work done so far as well.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

23,457 views 2 7
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