-
Suggestion
-
Resolution: Unresolved
-
None
-
204
-
91
-
Hello all,
Thank you for watching, voting, and commenting on this issue.
We use this data as well as many other inputs to feed into our prioritisation process. Having multiple subtask issue types is something that we may consider in the future, although it is not something that we will be focusing on in the next 6 months. We want to share this with you to ensure you can plan out your use of projects within Jira Software effectively.
In the short-term, we recommend teams use Company-Managed Projects if this is an absolute must for you. We apologise for the inconvenience this may cause you.
Please continue to vote and in particular please continue to add comments on how your team would find value when having multiple subtask issue types. This contextual information of what you are doing and why you are doing is invaluable for us in providing you with a product that will grow with your needs.
Thank you,
Eoin Ryan
Product Manager
Now, we have only a single sub-task issue type in Jira next-gen.
It would be great if the ability to create multiple sub-task issue types could be implemented in Next-gen.
- is duplicated by
-
- Closed
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWCLOUD-20901] Allow the creation of Multiple Sub-task issue types in Team Managed projects
This is a really needed feature. Under the story we need to raise bugs related to that story
Please add this feature. Team-managed projects are objectively superior in many ways and are vastly easier to manage, and yet, due to this limitation, they can only be used in limited circumstances.
This should be must have feature as most of us need defect as subtask on story
This would be great to have. XRay have a sub-test execution type that can't be used, presumably because of not able to have multiple Subtask in team managed. XRay test executions have to be used in team managed which are only linked to a Story so are not displayed underneath the Story on a Scrum Board when grouping by Subtask
+1 Last update was September 2022. I think it might be time to revisit.
It is such an inconvenience, people are requesting this since 2018.
It'll be great to have this feature, we can use it for testing types, and we usually have Story bug subtasks, so you can see the bugs under a story in the board instead of at the bottom and not connected to the story. Please add this.
This would help our team IMMENSELY. I don't really get why it's not available for team-managed but it's available for company. Please make it available!
I would really like to see this feature as it would allow us to add Defects, Questions, Observations as Sub tasks and it appears under story. This will add more visibility to the board, and also easy to create related Metrics.
+1 from me as well. I would really like to see this feature as it would allow us to add a specific sub task type that represents questions on a board used for user requirement tracking
+1 This seems like an easy win and would make a world of difference for us
+1 amazing that this hasn't been implemented yet. I need to create different types of testing subtasks as part of a bigger testing task.
+1 This would be great when Teams need to create tasks with subtasks that have specific requirements. This would allow us to create automations that run against those created subtask types.
This would be useful to differentiate sub-tasks for different types of tasks, differentiating testing tasks, sub-tasks, and development sub-tasks.
It would be nice to have different kinds of subtasks for one task, Not only because of different icons but because different custom fields are needed for different activities in our use cases. (no I wouldn't like to use forms. 
)
We've added a custom field onto the subtask issue type to allow us to tag it as a bug, but it still has the default subtask icon and isn't as nice a solution for reporting or general clarity/usability.
It's surprising that a company worth $62bn isn't capable of implementing this feature despite nearly 800 votes for it.
Looking back on it, one gets the impression that this is a deliberately overlooked functionality 
I want to add sprint bugs under the story to have them visible better on the board and easy to filter. I don't get why it's allowed in company-managed but in team-managed projects, it's still not. And no update nor other solution since September 2022 
why is doesn't allowed yet?? team project is too hard to manage the board.. too many restrictions.
@purwi.tivari
I suggest using common linking between issues on the same level. You can link the Story with the Bug and use this hierarchy viewer to improve and manage the dependencies https://marketplace.atlassian.com/apps/1211022/links-hierarchy-full-dependency-and-link-viewer?tab=overview&hosting=cloud
As sub-type can't be added in team projects, do you suggest any other way that my team can add bugs/improvements which are part of a story?
Want to understand the alternative suggested by jira as the feature is not available YET
also is there any update on this, as last response from Atlassian is almost 1 year ago
I need this to report bugs under stories. Bugs should be of different type than regular subtask.
What is the reason Atlassian allows new sub task types for company managed software and not team managed software? I understand that you cannot add these custom sub tasks to team managed even if you have them for company managed right now, but I'm wondering what the reason behind this was? Maybe that will help us understand and create better standard processes moving forward. Because of this discrepancy, we cannot have the same standard processes and workflows for our projects. Having a bug subtask is pretty common, and I'm interested in learning why its allowed for company and not team.
Voting for this also - it would be extremely helpful to have diff subtask types
My team wants this for managing staff check-ins. We'd like to have a variety of subtask types against a single employee task.
This is so heavy needed, I've been waiting for this feature for years.
I can't add sub-bug to story right now, and it blocked me for YEARS from using team-managed projects.
If anyone from Jira team read this thread - lack of this feature in team-managed projects is a sole reason why I've been moving most of my projects to Clickup and other project-management tools.
Now I have to work with Jira again, and it would be highly appreciated if you could add it.
Thank you,
Vova
I agree this would be very useful, in my team we want to have multiple sub-task types, and currently we are only able to create 1 subtask type which is not desired.
I should qualify because I missed "team managed" in the title previously. I'm using a company managed project,
Hi. New to the thread and came across it as part of my search on next steps. I was able to create the new SubTask Issue Type. All good. However, I don't know where to go from there. How can I associate this new SubTask Type with a Story. In short I want to be able to associate multiple SubTask Types (Default SubTask; Ideation SubTask) with a Story.
The reason for doing this is I "believe" I need to track the two SubTasks Types separately because of the way Boards work.
The above is a solution for a company managed project.
It is not a solution for team managed projects.
You should be able to update the icon as well. Now that you have added the issue type, go back to where you added it.
Gear icon, issues, issue types, and find the sub-task issue type you created.
Once you find it click the 3 dots to the right (...) followed by edit.
In the edit screen you will have the Issue Type Avatar option. This will allow you to setup the desired logo/image.
@leifvanart
Thank you. I did that, but on the board it is looking exactly the same as all other sub-tasks, so it is still hard to distinguish visually. I would expect from Jira team to at least provide the ability to change this icon as well then from blue sub-task 
to a red bug icon as I am still forced to pre-text the description with "BUG" to make distinguishable...
@Admin,
You will need to add a different sub-task issue type to the configuration.
Jira Site Admin required:
Browse to Jira
Click the gear in the upper right
Click Issues
Click Issue Types (left side)
Add new subtask issue type
Associate issue type with your project
(Going off memory here but that should get you there.)
Hello. Please make this happen.
I am in a Company Managed Project but I still don't see an option to add a bug/defect under a Story.
If I click on "+" sign, it just adds another sub-task. There is nothing in options ether "..."
Please advise.
Thank You.
How do we unsubscribe from this thread? It's become sad how long this seemingly "self-evident" request has existed.
Look at the history. The first request was made in August of 2019. This August will be 4 years and there's no indication it will happen anytime soon.
Atlassian doesn't value this. If you need it you'll need to seek a different product.
My team could benefit from having the ability to create subtasks as a child issue for QA purposes. It's faster that way, instead of having to create a separate ticket and link them.
Need this as well. (side note: the standard features in other team managed project types would be great.)
This request is here since 2022, any likelyhood it will come in 2025? I do like the NG project setup a lot but urgently miss this feature