Automation issue distribution

[박성민_학해_]

I want to create automation that distributes generated issues more to specific people rather than distributing them equally.

[Matthias Gaiser [K15t] · Accepted solution]

Hi @박성민_학해_

it's up to you how you want to create an Automation rule.

Do you have concrete criteria how you would like to distribute them? Some examples might be:

• all issues with a certain component, e.g. UI to person A
• all issues with a certain label to person B
• all issues with a certain label and custom field set to a specific value to person C

If you tell us your criteria, we might be able to help you design your rule.

Cheers,
Matthias.

[박성민_학해_]

Hi, @Matthias Gaiser [K15t] 

For example, four agents split the service requests equally and each took charge of 25% of the work.

However, I would like to distribute 30% of the work to better-skilled people and only 20% to less-skilled people.

There is no distinction between issue types or request types. They all handle the same operational issues.

--------------------------------------------------------------------------------------

Because we have criteria for assigning to users with the fewest unresolved issues,
For example, if the best person resolves outstanding issues quickly and there are few outstanding issues,
You will receive more distribution than others.

You can proceed using these rules, but
Is there any other way?

[Matthias Gaiser [K15t]]

I have to admit, I don't have a clever solution to these requirements.

I think, I'd go the other way and let people take up their requests, so they can assign tickets to themselves when they're done with one. This way, the load between the agents should be balanced based on how much effort a ticket requires.

[박성민_학해_]

@Matthias Gaiser [K15t] 
I agree with your opinion.

Thank you for answer :)