I have some questions if someone can help me out... * Are subtasks even a thing in JIRA Service Management Cloud? Looks to be a feature of JIRA Software * I looked in Automations and as of today, the create sub-task option is no longer under the Issue Actions category. Looks like some of it was available on on-premise versions of the software than was in the cloud project but is now gone. Can anyone confirm? Thanks :D

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

Creating sub-tasks

Todd Humphrey_pyl3dd

I have some questions if someone can help me out...

Are subtasks even a thing in JIRA Service Management Cloud? Looks to be a feature of JIRA Software
I looked in Automations and as of today, the create sub-task option is no longer under the Issue Actions category.

Looks like some of it was available on on-premise versions of the software than was in the cloud project but is now gone. Can anyone confirm? Thanks

Accepted answers

Nic Brough -Adaptavist-

Sub-tasks are not that useful in service-management, but you can use them in Jira.

Consider what your helpdesk is trying to do - it's usually "act upon someone asking for something", which is rarely a task you would fragment into sub-tasks. That's not saying it's "wrong" to do it, it can work well for some teams, just that you should think about why you think you want to - it's quite likely that you actually want to create issues for other teams in other projects.

Anyway, to use them, all you should have to do is make sure that there are one or more sub-task types in your issue type scheme for the project.

All comments

Todd Humphrey_pyl3dd

I also don't have this option... What am I missing from my setup?
It's almost like Subtasks are not assigned to my project.

Nic Brough -Adaptavist-

Sub-tasks are not that useful in service-management, but you can use them in Jira.

Anyway, to use them, all you should have to do is make sure that there are one or more sub-task types in your issue type scheme for the project.

Todd Humphrey_pyl3dd

Thank you for your quick response. In this case we'd like sub-task for request from HR to create a new user, that uses automation to create "New Laptop", "Add to Active Directory", "Setup Email" etc... sub-tasks.

I've looked at the issue type scheme, and I think that is where the problem is...

I can't assign the scheme to a project. Get message below.

Nic Brough -Adaptavist-

I think you've hit on the main use-case I'd argue for sub-tasks in service-management projects. "Raise a request for something with compound needs". A new user is probably the best example. They'll need accounts, equipment, access passes and and and.

Your issue type scheme is exactly where you need to be looking, but the "no projects available" is worrying; it suggests you've only got team-managed projects in your system.

That could be wrong, there might be something else blocking you, I'm not sure

I would want to go to the project within which you want to use sub-tasks and look at its configuration. If it is a company-managed project, you should be able to choose new schemes for it.

Todd Humphrey_pyl3dd

I think I found the answer... I guess with the next-gen project template we used, it was assigned as a team-managed project. Le sad... lol

I've found this thread I will review, BUT have concerns about migrating.

This is the biggest one.

Project and issue keys: Project keys are unique and can never be reused in Jira. If you migrate your issues to another project, they will get new keys and the new project must have a different key of its own. If you migrate your issues using the process above, Jira will automatically redirect any links to your old issue key

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

@Nic Brough -Adaptavist- Thanks so much for your time today!

Joseph Chung Yin

@Todd Humphrey -

I agreed completely with what @Nic Brough -Adaptavist- stated. If Subtask issue type is not available for your project, here is what you need to do (Only available for Company Managed project types)

1) Project settings >> Issue types

2) In the Action button, select "Edit issue type". Afterward you can select to include "Subtask" issue type to your project if it is not already there in your Issue Type Scheme Configuration.

In regards to Automation for Jira actions, again for Company Managed project types, Create Subtask action is there. This is not the same for Team Managed project types.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Joseph Chung Yin

@Todd Humphrey -

Please take a note of my suggestion regarding to automation for Jira actions difference between Company Managed vs Team Managed + you cannot expose subtask against Team Managed projects.

If my suggestions helped you. please click Accept answer when you have a chance.

Best, Joseph

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management