nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation to check mailconnector

Evert Morren

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.

Accepted answers

Evert Morren

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.

Regards.

All comments

Bill Sheboy

Hi @Evert Morren

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".

Kind regards,
Bill

Evert Morren C

Hi Bill, true, the summary must unique, but how can I search through the issue to find this specific issue?

Bill Sheboy

How many of these "canary" issues do you expect to exist at one time? If only one then:

trigger: issue created
condition: summary = "mail connector TEST issue"
action: delete issue

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"

Evert Morren

Hi Bill,

The trigger "issue created" doesn't work, if the mail connector doesn't work there is no issue. The trigger must be sheduled. I made a sheduled rule but get the error message:

It seems not possible to trigger a scheduled rule without a JQL statement?

Evert Morren

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.

Regards.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

automation