Dear all,

I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

Sincerely,
Aakrity Tibrewal
Jira DC

This is typically a reason for my frustrations with Jira. Everything has to be decided first and then everything is immutable. The difference between initiative, story, bug or task is minor from the user point of view. Then you discover you can't change such minor difference without recreating the entire story from scratch ? non sense to me.

Is this still under progress?
I'm facing the same issue where some of the Eng team members have created tasks as initiaitives. There is a heavy discussion thread int he comment section. So, I can't create a duplicate item as task without losing all the context in the initiative.

I ran into this today when a user asked about converting a bunch of Epics to Stories.  Easy enough (bulk edit/move) except that some of the Epics already have Stories and he wants the Stories to become sub-tasks, like this:

Epic -> Story

Story > Subtask

But when you turn epics to stories the links to their former child stories are broken.  I'm trying to figure out a workaround.

I was quite surprised to find out that I can't event change the sub-task type once it's created. If I need to switch the sub-task type I have to copy all the rest of information.

It's time-consuming and frustrating.

Being able to switch Projects as well, when the plan is sourced from multiple projects would be a big help.

Often during planning we move epics around to teams based on the work contained within them, which is discovered during a planning session

I support @Soumyashreehv comment

I have the same issue. I had a lot of people create issues as Initiative and after discussions, we now think these are epics/ features and there is no easy way to modify. I am surprised that this is open for more than a year now with this still in backlog!
Hoping for a quick resolution.

I agree with mark, the ability to transform a sub-task into a task is nice, but what about the other way around, to make a bunch of related tasks sub-tasks of an existing task.  For instance bugs that are part of another task, but don't realize they are until later, then want to associate this a sub-task.  Not sure how to do this without recreating...

Please note that Jessica's request is off-topic... the original request is still open -> it is really clumsy to copy the text, delete an item and add a new one just to promote or demote it in the hierarchy.