Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

SubTasks on Jira Service Desk

In our enterprise roll out of service desk we've run into scenarios where requests have multiple sub-tasks or components that relate to the the parent task. For instance if you are moving a series of workstations or installing to multiple locations for a whole team. This would be easily accomplished if the requester had the ability to add sub-tasks to the the main task. Each sub-task might include a workstation ID, Hostname, user, new location... etc. Jira is absurdly flexible when it comes to issues and the fields supported but the only way to make this happen is to provide access to the full Jira interface which is defeats the self service model. Has anyone else run into this situation and how was it overcome?

1 comment

Hi Joel,

Sub-tasks can be added by the agents to an existing request.  But they are not currently supported in JSD from the portal.

You can use automation or post-functions to create a standard set of sub-tasks based on a request.

Hope that helps

Susan

Thanks Susan for the quick reply. I understand they aren't supported out on the portal. I thought about automation but i don't know how you would automate the creation of a series of subtasks that would be different on a case by case by case basis. Take the example I gave in my post. If we're moving workstation of a group of 30 users. I want to be able to track their workstation id's old and new, their username, and their location id's old and new. How would i do that on the portal? 

The current portal is pretty limiting in this regard. ... that is unless I'm missing something here.

Hi Joel,

I think the thought is that the service desk should handle the initial request but that it would link to other projects or issues that would break it down further for other teams for example.

Susan

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Service Management

Announcing Jira Service Management!

Hello there Cloud Community members! Today, we’re thrilled to announce Jira Service Management, the next generation of Jira Service Desk. Jira Service Management touts advancements in IT service ...

1,358 views 16 33
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you