Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Multiple service requests from 1 request

Apologies in advance for an odd question - I'm a Confluence person trying to find possible solutions for the test team and I'm unfamiliar with JSM :)

Is it possible to have 1 service request raise a set of related requests?

Scenario is that a new starter will need to raise 6 service requests to get access to multiple systems. There might be 3-4 different standard sets of systems needed, based on role. 

How would you automate the process of raising multiple requests for the same user for different systems? Ideally they'd avoid duplicate data entry while still having individual service request IDs for each system for service desk admin purposes. 



2 answers

Hi @Jasmine Andrews ,

That is certainly possible. Automation has plenty of capabilities to cater for your need. It is just a matter for you to decide whether you want to work with linked issues, or e.g. with sub-tasks. If the people responsible for doing the work are all agents of your service desk, sub-tasks will work fine. If not, linked issues may be a better solution.

For some inspiration on how to automate all this, have a look at the Automation template library. These rules may come pretty close to what you are trying to achieve:

Hope this helps! 

Ah yes thanks I had seen sub-tasks but wasn't sure if that was going to cause hierarchical problems of some kind if requesting access to 1 of the systems was also considered a stand-alone request. So automating linked issues is looking like a really good option if sub-tasks aren't appropriate. Thanks @Walter Buggenhout _ACA IT_ 

0 votes
Stuart C Community Leader Nov 10, 2021

Hi @Jasmine Andrews 

You could use Jira automation to create the new requests based on the user raising a single request from the portal. As shown below you can use a condition that will only run when a defined request type is raised.


In the example above only one sub-task is created but you can add as many as you like, and define the fields to be populated automatically.

Thanks @Stuart C

I had wondered if automation was possible. This is probably the right direction to pursue.

Suggest an answer

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

JSM Jira Automation: How to Send SLA Breached Notifications

Hi Everyone, In   this tutorial,  we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached.   SLA Threshold Trigger The SLA t...

610 views 5 12
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