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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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

Updating Request Type in JSM when Issue is Created in Jira (i.e., Channel = Jira)



Good day! We are trying to update the Customer Request Type field via a workflow post function.  I know that this is easily achievable via automation (Action = Edit request type) however by using this solution, we are experiencing an issue when sending out the Approval required customer notification.


As an overview, we are creating record in our Service Management project not always from the portal but sometimes from Jira itself.  When creating records from Jira itself, the Customer Request Type is left blank thus customer notifications are not being sent out.  As an initial workaround, we created an automation to set the Customer Request Type when an issue is created from Jira (i.e., Channel = Jira).  This solution works perfectly when the approvers of the record is also set via one of our automations. 


However, we have a specific record where we had to pull the approver from an attribute of an Insight object and we were able to do this via an Insight Post function in the workflow itself.  This is where we're having an issue where the Approval required customer notification errors out because the Customer Request Type is not yet set when the approvers were set.  


We are now looking for a way to include the update on the Customer Request Type field via an Insight Post-function using a groovy script.  I was trying to achieve this by using "getRelevantConfig()" and "getOptions()" but I couldn't make it work :(  Is this even achievable? 


Alternatively, is there a way to somehow "delay" the customer notifications so that the necessary fields are already updated before trying to send the customer notifications? 


Appreciate any input.




0 answers

Suggest an answer

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

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

235 views 1 6
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