For Sub Tasks - how do change the workflow for when it is originally created?

[Jesse Anson]

Right now when a subtask is created it is using the same workflow as a regular standard issue. Overall is this fine except a subtask doesn't need to go through the whole workflow as a standard issue. So how do I change this? Also on the same note any way to have a standard story with tasks move along with the tasks in status updates?

thanks

[Nic Brough -Adaptavist- · Accepted solution]

Change the "workflow scheme". The default one has a really simple "use the jira default workflow for all issue types", but if you define one or more new workflows, you can set up a workflow scheme that says things like "use my first new workflow for sub-tasks and bugs, my second new workflow for stories, and the default for all other issue types".

(caveat - I'm not that familiar with OnDemand - I don't know if you have the access to do that)

I'm not sure I understand the second question, but I thing you're asking to have something like "if parent issue changes status, all it's sub-tasks should move too"? If that's right, then the answer is "yes, with code, but it's complex". The problem is that the parent and sub-tasks can all be in different status, so you have to think about how to get them all to move, and if you're sure you really want to cascade a status down to subtasks, and so-on. The code will have to understand all of that and know what to do.

One *really* useful trick there though - there's a condition that was intended to stop people from closing parent issues unless all the sub-tasks are closed, but it's a lot more flexible and lets you block any transition on a parent based on any status of the sub-tasks. That might help?