JIRA moves subtasks created for stories to the backlog instead of the same status

[Deleted user]

If a story is in status of: Selected for Development, In Progress

then a subtask is created and would be placed in the backlog.  This does not mimic the status of the parent story.

How can I fix this issue?

[Alexey Matveev]

How do you create a subtask? Do you use an add-on?

[Deleted user]

I just click on create sub-task in Kanban board 

[Alexey Matveev]

I see. Then you do not have any add-on. You would need an add-on to synchronize subtask statuses with the status of their parent. For example, you could use Power Scripts, Scriptrunner, Automation for Jira.

[Deleted user]

when I create it, it goes to backlog instead of mimicing the status of story 

[Deleted user]

Is there any documentation regarding on how to this?

[Alexey Matveev]

1. Power Scripts and ScriptRunner are basically the same. You would need to create global transitions to each status and name them as statuses. You could add a condition for the transitions so that they are invisible for users. You could call these transitions with the same name as statuses with a suffix ("_t")). Then you would add a post function to the subtask creation transition. It must be the last one in the list. In the post function your would write a script. For Power Scripts, it would be like this:

autotransition(parent.status + "_t", key);

2. You could also use Fast Track Transition post function in ScriptRunner.

3. For Automation for Jira. You would create a rule where you would check the status of the parent issue and perform the necessary transition.

I do not know any documentation which would give a detailed explanation on how to do it. You need to go through the documentation for the plugins.