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

Use the name of Request type as a condition in an Automation?

Ben Radlinski February 15, 2023

I am trying to create an automation that assigns a ticket to an Agent depending on the Request type the customer uses at the Portal. All of the request types on this portal go to the same Issue Type, so I can't use that as a condition. Is there a way to use the Request type names in the Portal to trigger an assignment?

2 answers

1 accepted

1 vote
Answer accepted
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2023

Hi @Ben Radlinski and welcome to the community!

Yes you can.  I see you're on Jira Server so this assumes you have the Jira Automation app installed.  It would look something like this:

  • TRIGGER: Issue Created
  • ISSUE FIELDS CONDITION:
    • Customer Request Type
      Equals
      Your Request Type
  • ACTION: Assign Issue (to your agent)
Ben Radlinski February 15, 2023

Customer Request Type was the key! Thank you so much. I'm new-ish to Service Desk, so I feel lost sometimes. Thank you.

Like Mark Segall likes this
Ben Radlinski February 15, 2023

While I have you, can this be done with Request Type Groups? I can't seem to find a field with that information.

Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2023

That's a great question.  If it is possible, you'd need to use an advanced compare condition.  I know it's possible to extract the group IDs, but not the actual names.  Here's how that would work:

{{issue.customer request type.requestType.groupIds}}

I can see value in something like this if the request type is only associated with one group.  However, multiple groups would make things complex.  So, assuming your request type is part of portal group "General" and that group has an ID of 10.  You would change your rule to something like this:

  • TRIGGER: Issue Created
  • CONDITION (Advanced)
    • {{issue.customer request type.requestType.groupIds}}
      Equals
      10
  • ACTION: Assign issue (to your agent)

I would be curious if smart values can actually pull the name of the group, but ID can work too.  You just need to do a little more digging.

Like Ben Radlinski likes this
Ben Radlinski February 16, 2023

Using the individual Request types ended up being the better long term option, so I'm sticking with that. Thanks again for your help.

Like Mark Segall likes this
0 votes
Theis Kvisgaard March 19, 2024

Related question:

Would it be possible to create a rule that triggers when the Request Type is changed to a specific Request Type?

 

Scenario: a ticket is created via email. The request type is then Emailed Request.

When starting to work on the ticket I edit the Request Type to the correct Request Type but this does not trigger my automations - because my automations that create sub-tasks etc. are triggered only when issue is created. Not if I change the Request Type afterwards manually.

Any way to make this work?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.20.12
TAGS
AUG Leaders

Atlassian Community Events