How to handle multiple fix versions with separate status?

What is the best way to handle the case where an issue will have multiple versions that need to be fixed?  Each fix will have it own workflow as they will need to be reviewed, tested and released separately.  Rules to meet are:

  • Initial fix version needs to be created automatically from affected version on issue creation.
  • When all versions have been fixed the issue is closed.
  • List of versions and their status needs to be available on issue screen.
  • Since every issue will have multiple versions to be fixed this needs minimal user interaction.

 

 

1 answer

0 votes

Create a sub-task for each version.

Jira can be set to close the parent when all subtasks are resolved, it will list them, with status, in the subtask section, and you can keep it really minimal with just status and a single version field and an open/closed workflow. 

Heck, if you want to automate, you could write a script that has a rule for which versions you need a sub-task for, and automatically create them, then have Bamboo move the sub-tasks to "test" or "closed" when a build and test run for a version says it was successful

Suggest an answer

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

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

442 views 7 5
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