How do I remove version from a task/ story when converting it to a subtask?

[Pooja Heda]

We manage project work through Releases and want only those items to show up in the list which have a version. So mostly need to see main tasks/ stories in the version. When we convert a task to subtask, the field value is retained and then even subtasks start to show up in release. Is there any rule we can add while converting tasks to subtasks or how can we handle it? Currently, we have to manually ensure that the field is updated before converting which is prone to lot of errors every time. 

Any inputs will be appreciated! Thanks in advance.

[Bill Sheboy · Accepted solution]

Hi @Pooja Heda 

To save you some time of ideas that do not work for this use case, automation rules are unable to detect the change to/from a sub-task for issue type...and according to this timed-out defect, Atlassian does not plan to fix this issue based on their current capacity/roadmap: https://jira.atlassian.com/browse/JRACLOUD-74536

There is still an open issue in the Code Barrel backlog for this: https://codebarrel.atlassian.net/browse/AUT-1960

Kind regards,
Bill

[Bill Sheboy]

Thinking about this one a bit more, I realized there is a work-around with automation: create a rule with a scheduled trigger to clear the field.

• trigger: scheduled (as often as you wish, such as once per hour) with JQL to find issues to update

project = myProject AND issueType = subtask AND fixVersion IS NOT EMPTY

• action: edit issue to clear the fixVersion

[Callum Carlile _Automation Consultants_]

Hi @Pooja Heda 

Have you considered removing the fix version field from sub-tasks? This would work if you never add sub-tasks to the releases.

[Pooja Heda]

Yes, sub-tasks do not have this field. Isn't there any solution that Atlassian provide for this issue? Strange!