Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,300,977
Community Members
 
Community Events
165
Community Groups

Not able to create another type of Sub tasks

I'm using the trial version, but need another sub-task category

2 comments

Hello @Bhumika Taunk 

Welcome to the community.

What steps are you executing to try to do this? What problems/errors are you encountering?

Welcome to the Atlassian Community!

My guess is that you are using a "team managed" project.  These only support one sub-task type at the moment.  (You can check the project management type by looking at the bottom of the left-hand panel)

I have change the project to company managed,

I want to create a hierarchy of issues. i.e. Epic-> Story-> Task->Subtask, Kindly guide to create this in free version.

You can't do this, Jira software only does Epic -> Story -> Sub-task.  

If you want layers above Epic, you will need to go up to premium to get Advanced Roadmaps, or buy one of the apps that provided more layers (Big Picture, Structure etc)

Like Anna-BigPicture likes this

Adding to what @Nic Brough _Adaptavist_ said...

In Jira natively there are only three layers to the issue hierachy.

At the top is Epics. Epics are unique in that you can't create addition issue of this type.

The next layer is where Nic said "Story". You can create multiple issues at this layer, such as Bug, Task, and others with names that suit your process. Issues at this layer can stand alone, or can be children of Epics. Issues at this level do not natively support having a parent/child relationship with each other. Issues at this level are "siblings". Issues at this layer are the items that you track in your agile board, and to which you add Story Points and/or time based effort estimates for burndown/up charts (if you are using those agile concepts).

The lowest layer is Subtasks. You can create multiple issues at this layer if you want to identify different types of Subtasks (though apparently not if you are working with a Team Managed project). Subtasks are not stand alone items, and are always linked to a parent in the middle or top layer.

Those are the layers where Jira natively can recognize a parent/child relationship.

If you want to add another layer, you can do it artificially using the generic issue Linking functionality available in Jira.

You could create a generic link between a Story and a Task (which are natively "siblings") and you could use the naming of that link relationship to state that the Story is a parent of the Task. However, Jira will not recognize that as a parent/child relationship. None of the native Jira functionality that pertains to parent/child relationships will apply to that link.

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

191 views 2 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you