Problems with Converting Sub-tasks into Tasks (different workflows)

[jetlovers]

Hello all,

We have different workflows for sub-tasks and tasks, lets take simple example :

- For sub-tasks, "To Do" status is first status after creation 
- For tasks, "To Do" status is in the middle of workflow (requires approval, etc)

The issue is that user can create sub-task (it gets To Do status), and then "Convert it into issue" - sub-task is converted to task keeping "To Do" status, so it bypasses approval steps of tasks' workflow.

[Mathis Hellensberg]

Hi @jetlovers 

This is happening because you can only have one status with the same name. The result is that both 'To Do' statuses have the same exact ID and are being mapped accordingly.

To solve this you'll either have to create a new status for one of them with another name or make sure that the 'To Do' status for tasks is before the approval in the workflow.

Hope you can figure it out! :)

[jetlovers]

Hi, thank you for your reply.

We tried to use different statuses too, but in this case it is even worse - during conversion of sub-tasks into task, user can select any new status, bypassing all workflow logic

[Mathis Hellensberg]

I see :(

I'm afraid you'll then have to change the workflow for tasks so that 'To Do' comes before the approval phase.

There is a request to be able to set a default status when moving an issue, which would solve your problem. I would recommend that you vote for it here: https://jira.atlassian.com/browse/JRASERVER-59346

EDIT: I just now saw that the issue is closed. They wont be implementing that feature :(

[jetlovers]

Moving To Do in workflow does not really help - because sub-tasks can be converted from any status, including "In Progress" and so on

[Andrew Laden]

What @jetlovers  said is actually important to realize. When you move an issue from 1 workflow to another, you are basically given the option to move it into any point in the workflow. So regardless of state names, approvals etc. You can take an issue that is in a requires approval, move it out to a different project, and the move it back in at a state further down the line after the approval status. So you have to be very careful about who you give move issue rights to.

Luckily it will all be captured in the issue activity, so you can see who did the move, but preventing it is tricky.