how to move existing issue type at sub task level

[arti_b_patil]

Hello All,

I have issue type "Task" is created and at level of story on jira site
I want to move "task" issue type to sub task level, story will become parent for "task" issue type.
i looked for options in setting under work type but did not see any options to update it in such way. I tried to look on community post but does not found anything for jira cloud.
My queries are is above action is possible and if how to achieve it?

[Olga Cheban _TitanApps_]

Hi @arti_b_patil !

It's not possible to move a Task under a Story in the hierarchy. However, you can eliminate Task and add Checklists to your Subtasks. As a result, your custom hierarchy will look like this:

Level 1 - Epics
|-- Level 0 - Stories
    |-- Level -1 - Subtasks
        |-- Level -2 - Checklist items

In this case, Subtasks will take the place of Tasks (or rather the place where you wanted Tasks to be), and Checklist items will take the role of Subtasks.

Here's an example of what this can look like:

You can add such checklists to your Subtasks (or any other work items) with our solution Smart Checklist for Jira. It allows you to tag responsible people, add deadlines, and set custom workflow statuses for each checklist item. You can also add links, images, expandable detail sections for each step, and more.

All this gives you most of the functionality you would get with subtasks, plus some new useful features, such as reusable checklist templates.

Please let me know if you have any questions!

[Ivan Manolov - JXL]

Hey @arti_b_patil

As mentioned by @Trudy Claspill, what you are looking for is not possible out of the box.

If you’re open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your Jira data that allows viewing, inline-editing, copy-pasting, sorting, and filtering by all your work items' fields, much like you’d do in e.g. Excel, Google Sheets, Smartsheet, or Airtable. It also comes with a number of powerful features, including highly customisable work item hierarchies. 

These work item hierarchies can be based on Jira's built-in parent/child relationships (like task/sub-task, or epic/story), based on issue links of configurable issue link types or any combination of these.

I am not absolutely sure this is what you are looking for but you can see that a "task" is shown as a parent of bugs and stories, even though they are all "base issue types" in Jira - and that's because there's a certain issue link between them.

I should also add that JXL can do much more than the above: From sum-ups and grouping, to conditional formatting, or inline bulk editing via copy/paste.

Any questions just let me know,

Best,

Ivan

[Trudy Claspill]

Hello @arti_b_patil 

That is not possible.

Jira has 3 core item hierarchy levels:

Level 1 - Epics
|-- Level 0 - standard issue types (Task, Bug, Story, etc.)
    |-- Level -1 - subtask issue types

You cannot move a Type from Level 0 to Level -1.

You can convert individual issues from a Type at level 0 to a Type at level -1; i.e. Convert an individual Task item to a Subtask item.

For Company Managed projects you can have multiple item types defined at Level -1, so you could have a type name "Task" at level -1. But it would be treated like all other subtask type items.

Can you tell us more about what problem you are trying to solve by changing the hierarchy structure? Perhaps we can provide you with alternate suggestions that will help solve the problem.

[arti_b_patil]

Hello Trudy, thank you fo reply.
We have multiple issue type at subtask level.
yes, i want "Task" issue type to be acted as subtask on level -1 with other subtasks. 
However, currently "Task" is at level 0 and i want to move it to -1. 
I am trying to find a way for that. 

[Trudy Claspill]

Hello @arti_b_patil 

The answer is that is not possible. You cannot move an issue type from level 0 to level -1.

The solution available to you natively is to convert each issue that is currently a Task to another type that is already configured as a subtask.

You can find the Convert to Subtask function under the ... button in the upper right corner of the issue details view. When you do that conversion you will be required to specify another level 0 issue as the Parent of the issue you are converting to a subtask.

You can also use the Bulk Change feature and the Move option rherein to convert multiple Task issues to subtasks, if you have permission that make bulk changes.