First Part:
I have migrated numerous stories to a different version but that has not migrated the child subtasks of those stories. Many of the subtasks are tied to previous versions or no version at all. I am just now noticing this.
I am needing to query all the subtasks of the stories within the version I have just moved to and then migrate those subtasks to the same version of the parent stories. I am unclear how to accomplish this in JQL.
Second part of my question:
Is there a way to prevent this from happening in the future? Can I have a function that applies the fixVersion of a parent to a child subtask and then also have that fixVersion of the sub-task change along with the parent story's version?
@Zack Lindberg - I can point you to a direction to a solution. What you can use is an "issue function" command that pulls all the sub-task of stories or parents that are on a particular version. However, you will a add-on for this.
The 2nd question will be the same solution. What you will need to do is pull the sub-task of all those tickets and is bulk update them at one time.
Yes, there is way to copy the fix version. You can do this by a post function. When a parent ticket is resolve to a fix version, it will add the fix version to the sub-task. Its more practical the other way around. When the sub-task is finally fix or the final sub-task is done, the last post function will update the latest fix version from the sub-task. This will be another add-on like JWT.
Hope this helps resolve your issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.