Projects IT Service Management Project settings Ticket Assignment based on location

[Laxminarayan De]

Dear Support Team,

I hope this message finds you well.

I am writing to request your assistance regarding an issue we are facing with the "Ticket Assignment Based on Location" automation rule in Jira. We have currently added 64 out of the maximum 65 allowed components, and we are unable to create or add new rules due to the component limit restriction.

This limitation is impacting our ability to continue assigning tickets based on location efficiently. We would appreciate your support in one of the following ways:

Assisting in optimizing the existing rule to reduce the number of components.

Creating additional automation rules to split the logic.

Exploring if it’s possible to increase the component limit (if applicable for our Jira plan).

Please let us know how best to proceed. I’ve attached a screenshot for your reference.

Looking forward to your support

[arielei]

Hey @Laxminarayan De 

Try to use in the Automation "TimeZone", and create a rule based on that.

see here for more details:
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/

[Walter Buggenhout]

Hi @Laxminarayan De and welcome to the Community!

Probably something went wrong with the screenshot you're referring to as there does not seem to be one linked to your question.

Unless you can add that and without any insight into what your rule looks like at this point, splitting your rule would almost certainly do the trick. Assuming you are using conditions in your rule to determine how to assign based on location, as long as you keep the options separate across your rules, this should work.

Alternatives to reduce the number of components could be to:

• use a lookup table in your automation rule to map out the different options;
• use if ... else ... conditions so you can handle multiple options with a single component;
• map your locations and corresponding assignees in Assets, but that would require a premium plan

Maybe you already apply some of those workarounds, of course.

Hope this helps!