Can someone provide a possible solution to moving a version through statuses (To Do, In Progress, Done) as it relates to a QA workflow?
Currently we are looking at creating a new issue type (version) and creating a single issue that all of the defects can link to. This single issuee will move through the statuses to provide insight into the overall progress.
what you are asking for is something that many JIRA users are looking for and also something that JIRA does not provide yet out of the box because a project version does not have its own lifecycle.
Your idea to create just one Issue of Version IssueType, and linking the defects back to it, in my opinion, is the right path.
I also agree with having concerns about filters and reports because if you go with the Version Issue Type with subtasks solution you will have to create new subtask issuetypes for all your existing issueTypes and this will break all the filters and reports.
What you could try to do in the future is to automate the link establishment.
A possible way to proceed with the automation could be the following:
If you are looking to automate also the Issue Version creation when a new version is added to the project you can only use a service that runs periodically and creates the new Version Issue if not present. You are forced to use the service because JIRA does not expose yet a project listener.
For both the scripted service and the scripted postfunction you can both create a custom plugin or use Script Runner.
I hope this could help you and please let me know if you need more information about the possibility to automate the entire process.
I suggest you use JIRA Agile to do that. Assuming version is an issue type, You can create one version and add sub-tasks to it, and you will be able to view its progress.
When all sub-tasks are done, then you can mode the "version" to the Done column and complete your work.
I hope this helps.
Thank you we are using Jira Agile.
Do I need to create a new issue type for bugs to make it a sub task or can this be modified?
I am concerned that some of the built in functionality for bugs (reports, charts etc.) would need to be recreated for the new sub task.
You don't need to create any new issue types. You can create sub-tasks in any of the standard issue types, you just need to access the issue and select More -> Create Sub-task. Also, the reports will work for all the issue types in the system.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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