Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,698
Community Members
 
Community Events
168
Community Groups

Create Service Management request not setting fields when using JSON in the "Additional Field" field

I'm writing a rule in Automation for Jira that should create a new Service Management Request.  I need to include two cascading list fields in the new Service Management ticket.  However, after I put in my code for them, the fields are not being filled out on the newly created tickets.  

My automation rule is as follows:

Trigger: Issue Create

IF condition: Issue Type = "target type"

IF/Else Condition: Custom dropdown field = XX

Then "Create Service Management Request"

         I then select the correct project & issue type for the new issue
         I set the fields I want to copy from the Trigger issue -  and set all the fields to "copy from current issue"  - All of these fields copy over.  

         I add my JSON code to set the cascading fields based off the rule's trigger issue value.  

Both cascading lists are on the Create Screen for the issue type Service Management ticket & on the "create" screen that a requester would fill out themselves on the portal.

I know that my code should be good, because if I use the standard "Create Issue" action instead of the "Create Service Management Request" action, the newly created ticket has the two cascading list fields fill out correctly.  The reason I can't use the normal Create Issue is I need the issue to have a matching service manager ticket.  

My JSON code just in case there is something I need to do differently to get it to work on a Service Management ticket. 

 

{
"update": {
"Request Room/Service Request": [
{
"set": {
"value": "{{issue.fields.Request Room/Service Request.value}}",
"child": {
"value": "{{issue.fields.Request Room/Service Request.child.value}}"
}
}
}
],
"Agency and Client": [
{
"set": {
"value": "{{issue.fields.Agency and Client.value}}",
"child": {
"value": "{{issue.fields.Agency and Client.child.value}}"
}
}
}
]
}
}

 

 

The overall use case is that our requester can be asking for a service request over consecutive days and we need to track each day as its own ticket as different resources may be assigned. 

 

Any help on why the additional field JSON is not working on the create service management request action. 

 

Thanks

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events