convert subtask to story if subtasks and stories use different workflows in the same project?

[Steve Hooczko]

How can I convert subtask to story if subtasks and stories use different workflows in the same project? When I try to convert the subtask, the only option I get is to convert it to a task. If I do that and then try to convert the task to a story the only option I get is to convert it back to a subtask.

Thoughts?

[Trudy Claspill · Accepted solution]

Hello @Steve Hooczko 

Is this for a Team Managed project or a Company Managed project? That information is available by looking at the bottom of the navigation pane on the left while viewing the project.

Do the two workflows share any status values or are they completely different?

[Steve Hooczko]

Company managed.

Yes, they share status values.

Problem is that when I click on the subtask icon at the top, next to the key, the only issue type I can change it to is Task.

[Trudy Claspill]

Ah, I see! That is not the way to convert a subtask type issue to a base level type issue.

The hierarchy of issues is

Epics
|-- base level type issues (Story, Bug, and usually one named Task)
    | subtask type issues (one by default named Sub-task)

You can add more issue types with different names at the base level and the subtask level. 

To convert an issue from one of those levels to the other you have to use the Convert option that shows up in the context menu (the three dots) in the upper right corner.

If you click in the breadcrumbs you'll be given only the options for other task types at the same level as the one you are trying to change. It sounds like in your system another type of issue has been created at the subtask level and named "Task".

[Niklas Malmberg]

We're running a Team-managed Jira project and I encountered the same question today.
However, our system doesn't have 'Convert to Issue'. Instead, the solution was to go via the Move command. 
Once these, I could convert the Story to a Sub-task, and assign it to the proper new Story as it's new parent. Worked well too, once I found this. 

[Zachary Willard]

this is the answer for Team-managed Jira projects