Changing the type of issue

[Alok kumar Singh]

I converted one of the standard issues type to sub-task and now I want to get it back to standard issue type. How can I convert?

[Ramiro Pointis · Accepted solution]

I'm curious how this user change the type to a sub-task since that it's not possible. Adding something to what Bhushan said what you can do it's to create the new issue type and then move all the issues from the wrong type to this new one, so then you can delete the type without losing anything and without taking the risk of modifying the DB.

[Alok kumar Singh]

Thanks a lot Bhushan and Ramiro for replying back, but I really don't know how I changed it. But it has changed somehow.

[Ramiro Pointis]

Are there any issues assigned to this issuetype?

[Ramiro Pointis]

Then you can do what I told in my answer. Create the standard issue type and then convert those issues to the new issue type. Once you don't have issues with the wrong issuetype you can erase it.

[Alok kumar Singh]

Yes there are a few ones.

[Bhushan Nagaraj]

Oh ok I see what you are saying. The issue type itself.

Firstly I am not sure you you managed to change that since I don't think there is a UI to change Issue Type from Standard to Subtask.

You can change it in the database but make sure you try this in a test environment.

UPDATE jiraschema.issuetype SET pstyle='jira_subtask' where pname='Unit Test Solution'

If you do not have any issues assigned to it yet, simply delete and recreate as a Subtask issue type

[Bhushan Nagaraj]

Answered here by Nic

https://answers.atlassian.com/questions/80386/converting-jira-sub-tasks-to-parent-issues

[Alok kumar Singh]

I think you goy it wrong Bhushan, I had a standard Issue type Unit Test solution, I somehoe changed the type to subtask. Now I want to move it back to Standard type.

[C_ Faysal]

so a previous parent issue-type is a sub-task issue-type now?

did you clicked on "More Actions>>Convert to Sub-Task" by accident?

[Bhushan Nagaraj]

Faysal even I thought he was talking about an issue. But he is not. He is talking about the Issue Type itself that administrators can create.

Administration -> Issue Types

[Nic Brough -Adaptavist-]

Hmm, in that case, he's describing something Jira does not do. You can't change an issue type between parent and child. The closest I can think of is that you rename <sub task> to "fred", then rename a <top level type> to <what the sub task was> then rename <sub task fred> to <what the top level type was called before>