We have three teams releasing updates; Hardware, software, and firmware revisions. When defects are filed, the user needs to submit the version for all three.
I'm looking for an elegant way to handle this.
I see two ways to handle this so far
1) User the project versions, and create a version for each combination that is allows/supproted. Pros' include the project admin being able to add new versions. The biggest Con is that the list would get very long very fast.
2) Create 3 custom fields for this project only. That means project related names; hiding them in all the existing field configurations; adding a new proejct specific field configuration. Pro's include it reflects the way people think about the product under test (it has three versions). Con: new versions require a system admin to add to the custom field options, the custom field list get unwieldy, time to create is not ideal with all the updates to existing field configurations.
The ideal situation would be for the project to allow additional versions to be added. I realize that is pretty specific to our situation.
Any other option that would be easier?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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