When I create a sub-task from an Issue, the Create screen does not stay in that same sub-task.

James Breunig

In Jira Cloud, in a Classic Software Project, we have a list of subtasks to choose from.

When you select 'Create Sub-task', and choose the sub-task that you would like, the Create screen doesn't follow that sub-task and defaults to a different one on the list. The project uses several different issue types and corresponding sub-tasks and thus must use the same issue type scheme since they are all part of the same project. This issue type scheme has a list of different subtasks. How do I associate an issue type with one sub-task and then have that sub-task be the one that is already selected on its Create Screen?

 

Nic Brough -Adaptavist-

To get the message you are seeing, you must have different fields and/or workflow between different types of issue.  When you're trying to swap between them, it is realising there is a difference and hence giving you the error.

> This issue type scheme has a list of different subtasks. How do I associate an issue type with one sub-task

Simply put, you don't.   All sub-task types are available to create from any issue type in the project, they're not dependent on each other.  You can do some stuff in the workflow that would block the selection of certain types (specifically, a validator on create that checks the pairing and rejects the attempt to create, but this is not a nice thing to do to your people as the failure will lose what they've entered)