You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Some times our mailconnector fails. Therefore I tried to make two automation rules:
The first rule sends an email to the connector, with summary 'mailconnector check', this works.
The second rule must lookup if a ticket is created with the summary 'mailconnector check', if yes, the ticket must be deleted, if not then an email must be send to the admin.
How can I made a rule who is looking up for these specific ticket and if found it must be deleted.
Hi Bill, see below the details.
I have one ticket with the right description:
In this situation there won't be send an mail in my opinion.
After I deleted this ticket, the log file is:
Also in this situation a mail has been send. I don't understand what happens.
That is an interesting use case to check for availability. Well done!
To find your issue to delete, consider how to make it unique-enough to find while being different from people-created issues.
For example, perhaps put something in the summary you can test with a condition, such as "mail connector TEST issue".
How many of these "canary" issues do you expect to exist at one time? If only one then:
I recommend using a longer and more unique summary to reduce the risks of problems.
If you expect there to be multiple, and you want to remove them at one time, consider instead using a scheduled trigger rule with the JQL to find them:
project = myProjectName AND summary = "mail connector TEST issue"
Nope, you definitely can have a scheduled trigger rule without JQL.
And, are you using the Cloud or Server/Data Center version, as each has different batch processing options? For example for Cloud:
project = myProject
AND summary = "mail connector TEST issue"
AND ...any other criteria
This works for one-issue-found. If you possibly have more to delete, you will need a branch with the JQL before the delete action.
Hi Bill, Thank you for reply.
I have made the rule you suggested, but still the same error.
It seems, it is not possible to do actions on an issue, without the option to run JQL?
I try it with two rules, the first one send a mail if these is no issue (mailconnector doesn't work), the second deletes the ticket if there is a ticket (mailconnector works). The first one doesn't work, what do I wrong?
Can you help me?
Would you please post images of:
Ah! Smart values are usually case sensitive, and unfortunately do not show errors when you get the case incorrect. The smart value for Lookup Issues uses camel-case:
Please change your condition and see what happens.