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

Max
Contributor
November 1, 2024

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:

33333.png

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

444444.png

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?

1 answer

1 accepted

2 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 1, 2024

Helo @Max 

"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.

Max
Contributor
November 1, 2024

@Trudy 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_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 1, 2024

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

Like # people like this
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 1, 2024

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.

Like Max likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events