-
Sub-task
-
Resolution: Fixed
-
None
-
None
-
None
-
None
UPDATED: Sub-tasks are now available for most customers. You can learn more about it by reading this blogpost: https://community.atlassian.com/t5/Next-gen-articles/Introducing-subtasks-to-work-breakdown-in-next-gen/ba-p/1105389.
Please note that we have rolled out subtasks to almost all instances and we are in the process of completing the remainder of the rollout. If you are unable to add the subtask issue type, then don't worry it's coming very soon to your instance.
Problem Definition
The customer does not have an option to add an issue type: Sub-task in the current set of Next-gen projects.
The customer can create a custom issue type Sub-task, however, this does not solve the purpose of it.
Suggested Solution
Currently, there are no direct solutions as such, customers will have to create a non Next-gen project to use issue type Sub-task in their projects
Workaround
As next-gen project focuses on providing an easier experience to get started, please consider using classic project.
Refer to the document Migrate between next-gen and classic projects if you have some tickets on next-gen and need to migrate them to classic project.
- relates to
-
JSWCLOUD-17233 Unable to create Sub-task in next-gen project
-
- Closed
-
- is related to
-
JST-445511 You do not have permission to view this issue
[JSWCLOUD-17155] No option to add a issue type "sub-task" for next-gen projects
Remote Link | New: This issue links to "Page (Confluence)" [ 607934 ] |
Workflow | Original: GreenHopper Kanban Workflow 20141014 - Restricted [ 3075824 ] | New: JAC Sub-task Workflow [ 3475086 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Description |
Original:
{panel:title=(i) News | borderStyle=| borderColor=| titleBGColor=#e0efff| bgColor=}
UPDATED: [Sub-tasks|https://www.atlassian.com/roadmap/jira-software#results] are coming soon! {panel} h3. Problem Definition The customer does not have an option to add an issue type: *Sub-task* in the current set of *Next-gen projects*. The customer can create a custom issue type *Sub-task*, however, this does not solve the purpose of it. h3. Suggested Solution Currently, there are no direct solutions as such, customers will have to create a non Next-gen project to use issue type *Sub-task* in their projects h3. Workaround As [next-gen|https://community.atlassian.com/t5/Next-gen-articles/Everything-you-want-to-know-about-next-gen-projects-in-Jira/ba-p/894773] project focuses on providing an easier experience to get started, please consider using classic project. Refer to the document [Migrate between next-gen and classic projects|https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-a-next-gen-project-to-a-classic-project-957974933.html] if you have some tickets on next-gen and need to migrate them to classic project. |
New:
{panel:title= News|titleBGColor=#e0efff}
(i) *UPDATED*: [Sub-tasks|https://www.atlassian.com/roadmap/jira-software#results] are now available for most customers. You can learn more about it by reading this blogpost: [https://community.atlassian.com/t5/Next-gen-articles/Introducing-subtasks-to-work-breakdown-in-next-gen/ba-p/1105389]. Please note that we have rolled out subtasks to almost all instances and we are in the process of completing the remainder of the rollout. If you are unable to add the subtask issue type, then don't worry it's coming very soon to your instance. {panel} h3. Problem Definition The customer does not have an option to add an issue type: *Sub-task* in the current set of *Next-gen projects*. The customer can create a custom issue type *Sub-task*, however, this does not solve the purpose of it. h3. Suggested Solution Currently, there are no direct solutions as such, customers will have to create a non Next-gen project to use issue type *Sub-task* in their projects h3. Workaround As [next-gen|https://community.atlassian.com/t5/Next-gen-articles/Everything-you-want-to-know-about-next-gen-projects-in-Jira/ba-p/894773] project focuses on providing an easier experience to get started, please consider using classic project. Refer to the document [Migrate between next-gen and classic projects|https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-a-next-gen-project-to-a-classic-project-957974933.html] if you have some tickets on next-gen and need to migrate them to classic project. |
Remote Link | New: This issue links to "Page (Confluence)" [ 418366 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 418254 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 416503 ] |
Assignee | New: Eoin [ eryan ] | |
Status | Original: Awaiting Development [ 10038 ] | New: In Progress [ 3 ] |
Status | Original: Open [ 1 ] | New: Awaiting Development [ 10038 ] |
Remote Link | New: This issue links to "JST-445511 (Atlassian Support System)" [ 407168 ] |