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; } } }

Create ticket automation

Felipe Rodrigo Pinto Pereira de Lima

Great afternoon everyone.

I recently started working with Jira, and I haven't found any topic with exactly what I should do, to create an automation that creates tickets on the days I select, but doesn't create a ticket that already exists.
For example: I want to create a ticket every day at 06:00 AM with the custom field "Y" that contains the value "X", but if already have a ticket with the value "X" of the same custom field, then not create this ticket. Is it possible with a free license?
Here's a print of how I tried to do the automation, but it's not working.

If there is already an answer for this, I apologize for not finding it, I'm still new to the Jira community

Accepted answers

Trudy P Claspill

Hello @Felipe Rodrigo Pinto Pereira de Lima

Welcome to the community.

When you say an automation rule is not working, there is some additional information that we need to help you. Specifically, what do you mean by "not working"?

Is the rule not getting triggered?

If it is getting triggered, what does the Audit Log say? Notice "Audit Log" in the upper left corner below "Automation", your rule name, and "Rule Details"? Click on that to see the audit logs for each configuration change for the rule and each execution of the rule.

Can you show us the details of the Trigger? A Schedule Trigger can be set up to use a JQL or not use a JQL.

The component that follows is a Condition. That condition requires an issue to operate against. If you Schedule Trigger didn't include a JQL for selecting issues, then you Condition doesn't have an issue to operate against.

Regarding your condition:

" if already have a ticket with the value "X" of the same custom field,"

Are there any other things that need to be true about that issue, like the day it was created or its current status?

All comments

Felipe Rodrigo Pinto Pereira de Lima

Sorry, I almost forgot to post the image.

Trudy P Claspill

Hello @Felipe Rodrigo Pinto Pereira de Lima

Welcome to the community.

When you say an automation rule is not working, there is some additional information that we need to help you. Specifically, what do you mean by "not working"?

Is the rule not getting triggered?

Can you show us the details of the Trigger? A Schedule Trigger can be set up to use a JQL or not use a JQL.

Regarding your condition:

" if already have a ticket with the value "X" of the same custom field,"

Are there any other things that need to be true about that issue, like the day it was created or its current status?

Felipe Rodrigo Pinto Pereira de Lima

Sorry not to specify. It's not trigging. It just doesn't open the ticket. But then what I wish to do is possible?

But yes, I had forgotten the JQL part, and I sure wrote it wrong, but I don't know what to specify in the JQL according to the prints. Can you guide me exactly what I should write? See if these prints help you, please.

If anything is missing, I apologize, just ask and I'll look for it and put it here. Thank you so far for your help.

Trudy P Claspill

Hello @Felipe Rodrigo Pinto Pereira de Lima

The error is explained in the Audit Log. The JQL statement you have in your Schedule Trigger is invalid.

Screen Shot 2022-10-25 at 1.37.55 PM.png

However, I would recommend a different way to accomplish this with Automation.

When you set up a Schedule trigger with a JQL statement, that is usually done because you want to execute some operation for all the issues that are found by that JQL statement.

Instead I would recommend that you use the Schedule trigger without a JQL statement.

For the next component I would recommend the Lookup Issues action. You can use a JQL statement to search for issues.

Screen Shot 2022-10-25 at 1.43.40 PM.png

After the LookupIssues action I would add a Condition: Advanced Compare and check how many issues were returned by the Lookup Issues action. The value you want is the one that will indicate you DO want to proceed with creating a new issue. I would construct the JQL so that you would want it to return 0 issues.

Screen Shot 2022-10-25 at 1.46.20 PM.png

And then add the Action to Create Issue.

Felipe Rodrigo Pinto Pereira de Lima

Thank you very much for your help so far, but I still haven't been able to make the automation not open a ticket when already have a ticket with that name.

Now it's opening the ticket, it's not showing any error in the log, but the tickets are repeating, even though they already have one open.

To tell you the truth, I still don't understand what Lookup is doing.Can you give me more details, to understand what I'm doing wrong, please?

Here are some prints:

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud