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 Rule for multi condition multi values to set.

Shadd Schutte

I am working on an automation rule that will used the planned start and planned end dates to determine the Program Increment that an epic is aligned with. An epic could start in one Program Increment and end in another Program Increment, and I want to select both values. The field Program Increment is a multi-select field. The planned start is customfield_10101 and planned end is customfield_10102. The logic is working for the most part.

I am using If/Else statements to determine if the start date is after a specific date or the end date is before a certain date if it is select a specific PI from our list of options. This works but is only selecting the PI for the latest End date.

An example is I have and Epic that has a planned start in the middle of Program Increment PI2 2024 and a planned end date in early part of Program Increment PI3 2024. This epic is only getting set to PI3 2024 when I want it to select both PI2 and PI3.

Accepted answers

All comments

Bill Sheboy

Hi @Shadd Schutte

Rather than the JSON (with may not work due to field differences), please post images of the following for context:

an image of your complete automation rule, in one single image; that may require using a screen capture tool or browser addon for scrolling page capture
for any smart value conditions, include images of those
an image of the audit log details showing the rule execution which did not work as you expected

Until we see those...

I hypothesize your rule is either:

using contradictory if / else conditions, and / or
the rule updates the issue, but does not perform a re-fetch action before attempting another edit. (As a result, one of the edits is "walking over" the other.

Seeing your rule details will help to confirm (or exclude) these. Thanks!

Kind regards,
Bill

Shadd Schutte

Wrong window

Shadd Schutte

Here is a copy of the log for an Epic that should have PI1 and PI2 2024 just based on the planned Start and Planned End dates.

Automation Rule PI log.jpg

Here is the full automation rule sorry for being so long it is 8 increments with repeating logic.

Automation Rule PI full capture.jpg

Bill Sheboy

Those rule images are not readable to me as the resolution is too low. Would you please replace them with higher-res ones?

From the audit log image you show, it appears there is only one edit of the issue fields. Is that correct?

Shadd Schutte

I hope these are better I had to break it down into a series to make it readable.

PI Rule page 1.jpg PI Rule Page 2.jpg PI Rule Page 3.jpg PI Rule Page 4.jpg PI Rule Page 5.jpg PI Rule Page 6.jpg PI Rule Page 7.jpg PI Rule Page 8.jpg PI Rule Page 9.jpg PI Rule Page 10.jpg PI Rule Page 11.jpg PI Rule Page 12.jpg PI Rule Page 13.jpg PI Rule Page 14.jpg PI Rule Page 15.jpg PI Rule Page 16.jpg

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

jira-automation