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 Schedule Trigger Error No Message

Ann von Brincken

I am trying to create this basic automation, that every hour will add the epics labels to its card children. However, the automation won't publish. When I publish, it puts an error icon on the schedule. However, there is no error message. Any ideas what the problem could be?

Accepted answers

All comments

Sphinx13

Are you sure you have given your automation a name? Try returning to 'Rule details' and make sure all the required info are there. That is an odd error though.

Sphinx13

Tested this! some issue-specific actions such as edit issue will only work if you use a jql in the schedule. I'd say check the 'run jql search' box under your schedule trigger and add the jql "issuetype = card AND status != Done". Now there's no need for the two conditions, as the schedule will already filter only those issues.

Fred Momeni_33c0re

Hi Ann

The problem with the rule you have defined is that you don't have a "Look up" action. Every hour, it is executed, but you must have a JQL to select the issues you need.

You can also use a different trigger to run the rule when an issue is created.

I hope this has helped you.

Jaroslav Kalcinskij_16cmfc

Hey, I have the same issue as @Ann von Brincken

I'm trying to create a simple automation which will create an issue on first day of every month. When I try to publish the rule and turn it on, I get the same error flag in the trigger (schedule) component without any details to what exactly this error refers to:

Never had this issue before. Tried to use Advanced (CRON expression) instead but with no success.

Any ideas on what might be wrong here?

Trudy P Claspill

@Jaroslav Kalcinskij

Welcome to the community.

What is the workflow for that type of issue? Is To Do a valid status for the workflow? Is it the status that issues start in after being created? If so, you don't need to have a step to transition to that status.

Jaroslav Kalcinskij

Hi @Trudy P Claspill

Yes, To Do is a valid status in the Workflow for this type of issue. By default, issues are being created in Open status, and afterwards are moved to 'To Do' status.

Not really sure what's wrong with it. The same approach works in other automations rules but where triggers are not scheduled but, for example, 'Issue created' or 'Issue edited'.

Trudy P Claspill

I tried creating a similar rule (Schedule, Create Issue, Transition Issue) and got the same error. I'm not sure why that method is showing a failure icon when trying to publish, but I found a method that does appear to work.

Use a Branch / Related Issues / All Created Issues and put the Transition within the branch.

Screen Shot 2022-11-09 at 10.26.26 AM.png

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