Would it be correct to say that anything that needs its own Versions should be a project?
Currently my Jira instance has projects that consist of multiple components, and each component is released separately. This does not work well because all of the Versions are intermixed on the project's Versions page.
yes, I think that would be an correct assumption. It of course depends a bit on the components and how many you have.
If you use GreenHopper (agile) making a planning over multiple projects isn't a issue anymore. Thanks to the new rapid boards. So in this case I would suggest creating a few extra projects.
If you don't use greenhopper at all, using the a cascading select might be the best workaround for you -- as described here Another solution, if you only have a few versions, is to prefix your version by component. ie compa-1.1 and compb-1.1. It's not perfect, but sorting is a bit easier ;-)
We have developed a JIRA plugin that allows component specific version numbers. It enforces component specific versions on issue create, edit, inline edit and workflow screens. You can check it out at Atlassian Marketplace (Component and Bundle Versions for JIRA) or at read the plug-in's help page for more detailed manual.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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