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; } } }

What is the difference between "Sub-task" and "Subtask"?

unknown

On one of my test project I've noticed that the "Subtask" is one single word.

Kindly have a look, it's TEAM managed project:

Another project got this type of issue like following: "Sub-task". It is COMPANY managed project:

It could be I've created this type, and simply forgot about it ^_^

Or this is the Jira settings by defoult?

Could you help me to get it?

Accepted answers

Trudy P Claspill

Helo @[deleted]

"Sub-task" is the default name for the subtask issue type that is used by Company Managed projects. This is created out-of-the-box by Jira when subtask functionality is enabled at the global level.

"Subtask" is the default name for the subtask issue type that is created automatically within each Team Managed project.

All comments

Trudy P Claspill

Helo @[deleted]

"Sub-task" is the default name for the subtask issue type that is used by Company Managed projects. This is created out-of-the-box by Jira when subtask functionality is enabled at the global level.

"Subtask" is the default name for the subtask issue type that is created automatically within each Team Managed project.

unknown

@Trudy P Claspill Thank you. I was thinking I had done something wrong.

I just can't get the reason of this separating "Subtask" and "Sub-task" issue type. For what this was created?

I think I can delete "Sub-task" on company managed project and add the new type, like on team managed. To make it looks the same on the different project type.

I am going to do it on my test account. But could it be not the best option?

Matt Doar _Adaptavist_

There may be other parts of Jira that use the name "Sub-task" hardcoded. I wouldn't delete it myself out of caution

Trudy P Claspill

I just can't get the reason of this separating "Subtask" and "Sub-task" issue type. For what this was created?

I am not an employee of Atlassian, and I don't have any special insights as to why they made this design choice.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud