nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adding subtasks to issue - child the same?

Jim Stewart_1wcyht

I'm working on a team-managed project. With some of our issues, we may want to have subtasks. I note that in company-managed projects they're called subtasks. But they seem to be called 'child' tasks in the team-managed version. Am I understanding that correctly? That they are essentially the same thing but are (for whatever reason) named differently? Or are they different things?

Accepted answers

Jack Brickey

Sort of…kind of…yes…almost 😉

Child obviously is a more non-specific term. However in TMP a story can be a child of an epic and a sub-task can be a child of a story or task. I think that the more nonspecific terminology works a little bit better to be honest.

All comments

Jack Brickey

Sort of…kind of…yes…almost 😉

Jim Stewart_1wcyht

Ok. so for all intents and (our) purposes, they are the same if I understand correctly. Interestingly, in the intervening time, I did a little research. The word sub-task (spelled that way) not only shows up in Issue Types but is enabled. All systems seem go. But when you go to add subtask your only option is 'child' as if somewhere along the way it got renamed or translated if you will.

Jack Brickey

yes the same. yes confusing too.

Jim Stewart_1wcyht

Odd. Ok. Well, I've played around with it and it seems to work ok. Maybe add that one to the 'hey guys, let's name it one thing or another' pile. 😊 Thanks.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud