I want to solve the duplication problem

[Gustavo]

My project was created with the aim of creating internal maintenance calls in our transport company, so the reporter creates the call with the vehicle's license plate and selects the workshop where the maintenance will be carried out. So when they end up creating 2 calls sometimes to the same workshop, I wanted to know how I can resolve this automatically without having to notify them about the incident

[Mikael Sandberg]

You can do this via automation and smart values. The smart value would be used to extract information like license plate and workshop, then use that as part of a lookup issues to see if it returns more than one, and if that is the case close the duplicate issues.

[Gustavo]

and what would that look like, I did an automation based on this and was unsuccessful

[Mikael Sandberg]

It would look something like this:

This example is looking for issues with the same summary and if the returned lookup issue size is greater than one it will close those other issues.

[Gustavo]

Perfect, I believe that today it is not possible to create a trigger to avoid the creation of an item if there is already another one (avoiding duplication), but however this way I already achieve something, I think I will create another status in the project with the name DUPLICATE to make it easier to deal with

[Mikael Sandberg]

Instead of using a separate status for duplicate you could use Resolution, that is what I use in the example automation above. 

[Gustavo]

Hello, I saw that I was going to have some problems with the rule, so I needed an intelligent value for the WORKSHOP field, so that when it is EQUAL, in 24 hours and the summary is the same too, it executes, because today this is how the rule is it will cover old items, as the same vehicle will have several so-called