Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

What configuration affects if a story can have child tasks?

Martin Honek October 4, 2019

We have several next-gen projects in our Jira. I can create child issues in some of them, but not in one particular project. The button is just not there:

https://i.imgur.com/CVfTVDP.png

 

At first I thought I lack privileges to do so... but I am a member (and even an admin!) in that project, so this is clearly not an issue.

I tried to work around this - to create a task and "add a parent" to it. Sadly, that option offers me only epic parents. I would like to have the usual hierarchy of epic-story-task-(subtask) instead.

What other configuration did I miss? Or is the issue, possibly, elsewhere?

1 answer

1 accepted

1 vote
Answer accepted
Ste Wright
Community Champion
October 5, 2019

Hi @Martin Honek

One thing worth checking is if the sub-task issue type is activated in that project:

  • Select Project Settings from the side-bar
  • Select Issue Types
  • Ensure sub-tasks have been added from the left-hand menu. If not, add it to activate child issues

^ This does hide the button if sub-tasks are not added. If this isn't the issue, let us know :)

Ste

Martin Honek October 7, 2019

I can see sub-tasks in that project's settings: https://i.imgur.com/EOeiqqV.png

Is there something else we need to do with them?

Ste Wright
Community Champion
October 7, 2019

Hi @Martin Honek

Are you sure that's not a custom issue type? Sub-task for Next-Gen is "Subtask" rather than "SubTask"

If you press the "+ Add Issue Type" button - is there another Sub-task issue type to add?

Ste

Martin Honek October 7, 2019

Nice catch! It was a custom type left over from past. The interesting part is: when I tried to add another type (like you suggested), I couldn't: https://i.imgur.com/8wOfGUj.png

I had to remove the old one, before I could add the new one. Having a custom "SubTask" type prevented adding the built-in "Subtask" type. I am not sure if that is the intended behaviour, or an obscure bug in case sensitivity... but thanks for the solution!

Like Ste Wright likes this

Suggest an answer

Log in or Sign up to answer