Subtask is define as « base type» and can't move it back to « subtask type »

[Marco Vachon]

For some reasons, the current issue name Subtack (the initial default name one) is of the type « Task » and not « subtask ». I don't see where in all the config I can change it back to « Subtask type » for the appropriated behavior. (one obvious consequence is that the « Create subtask » is not present in the task screen, since there is no « subtask type issues » at all for the project... except this confusing name)

-------

More Detail: 

So I am expending the use of a previously existing Jira (more Licence recently acquired, more peoples to use it, more internal support for it use). I want to use is as close as standard to start with. It is JIRA cloud and it has been around for a few years with limited use. (Read : It does not show many config change/personalisation, but obviously something was done to have the current situation).

Also: I have done some try out and minimum experimentation with another personal/just me as user JIRA Cloud (call it JIRA 2) and « out of the box » (Jira Software / Scrum), It behave exactly as I expected: Subtask is there, of the «Subtask type » and everything behave/show as expected in the product

So I can compare the two JIRA screen by screen, and I did dig into various configurations screen. I can see the effect of the difference, where is show me (or not) that Subtask is (or not)  of the type « Sub-task ». I just don't find a options/menu to change the « Name = Substack, Issue type =  base » to « Name = Substack, Issue type =  sub-task »

[Nic Brough -Adaptavist-]

You can't swap types - it would need to provoke an entire "move" process for all the affected issues, which is slow and painful - you'd need to identify a new parent for every issue currently of that type at the very least!

There is a very simple fix though.  Rename the current "sub-task" to something else.  Anything will do - "Penguin" if you feel like it.  Then create a new issue type called "sub-task".  And start using it!

[Marco Vachon]

Thank you, that is indeed our current plan B. It will required a bit more work and double check of a few thing. The 'new' subtask could end_up being name  «sub_task» and so on, but this is indeed  doable. Still, I like to understand how this happend at go back to as close a possible to default setting. Easier after to point people to generic documentation/video/formation about Jira.  I will invest a limited time to find the « ideal » solution before going to plan B / Good solution.

[Magdalena Zhisheva]

Hi @Marco Vachon

I am not sure if you can change it at all. 

What I would do in that situation is to create a new Sub-task issue type with the proper sub-task type, assign it to the same projects as the fault one and then delete it. 

As a final step, I would rename the "new" Sub-Task issue one as the "old" one. 

Hope it helps. 

If this post was helpful, mark it as Accepted solutions, so you can help others who may have the same difficulties.

If your question has not been resolved, please post again with more details.

[Marco Vachon]

As stated in a  previous reply, good plan B but with possible minors (?) consequences.  I will invest a limited time to find the « ideal » solution before going to plan B / Good solution.

as for « I am not sure if you can change it at all », well, someone did somehow in the other direction.

Note: I do hope the reason is not as (adjective here) and unrelated as the fact that we have change setting to French.