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

Possible Bug - JIRA Automation - Changing Occurrence Setting does not work correctly.

David Tieman

When changing the Occurrence value for a Automation Rule, the Next Run values are not updated correctly.

Situation: Rule was originally created on 4/1/24 (Monday) to run every 2 weeks on Monday.

This past Monday (7/15) I made a change to run every 1 week for a temporary change. After the rule ran on Monday (7/15) I changed the Occurrence value back to 2 weeks, expecting the Next Run date to be 7/29. However, the Next Run date was set to 7/22. I could change the day of the week value from Monday to Wednesday (as a test) and the Next Run date was set correctly, but setting the day back to Monday set the Next Run date to Monday 7/22. In talking to a co-worker he suggested changing the Start Date to 7/15 which "Fixed" this problem. BUT I believe this to be a BUG with the Calendar function in JIRA Cloud. 2024 just happens to be a LEAP year too !!!!

Temporary solution: Change the Start Date on any Automation to be a more recent value (7/15 happens to be the last successful execution date for this rule.

Can someone from Atlassian confirm if this is a bug or expected process for updating Occurrence values?

Accepted answers

Bill Sheboy

Hi @David Tieman

This may be a caching issue in the rule editor, or a defect from the recent changes to the Scheduled Trigger in the last few weeks. I looked in the public backlog and did not see this symptom.

I recommend asking your Jira Site Admin to submit a defect for this here: https://support.atlassian.com/contact/#/

Once you hear back from them, please post what you learn to benefit the community. Thanks!

Kind regards,
Bill

All comments

Bill Sheboy

Hi @David Tieman

This may be a caching issue in the rule editor, or a defect from the recent changes to the Scheduled Trigger in the last few weeks. I looked in the public backlog and did not see this symptom.

I recommend asking your Jira Site Admin to submit a defect for this here: https://support.atlassian.com/contact/#/

Once you hear back from them, please post what you learn to benefit the community. Thanks!

Kind regards,
Bill

David Tieman

Thank you @Bill Sheboy I will pass this along to our Admins... and thank you for the link for the Schedule Trigger updates, I missed this announcement.

David Tieman

@Bill Sheboy After submitting this issue to Atlassian as a potential bug, the response from the Atlassian team is that this is functioning as expected WITH an update to the Start Date field. The Start Date and Reoccurrence values for Weeks/Months are connected. It would be good for Atlassian to update their documentation to accurately/correctly state that the Reoccurrence values are tied to the Start Date of the Automation.

Bill Sheboy

Hmmm...okay. I could understand dependency between the fields in this trigger, however...

Recently I noticed the first field selected by the UX when a Scheduled Trigger is selected has some latency behaviors. What I observed was, with the latest Chrome browser:

create a new rule
add the scheduled trigger
click on the Occurrence: Run Rule Every... to select it
type in a number
start scrolling down to hit Next, and...
instead the UX clears my value from Run Rule Every, resetting it to 1, and focuses the cursor on the Start Date at the top of the trigger!

(sigh)

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud