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

Jira Automation fails to set active sprint

Brad_6guaep

We have a rule that automatically sets the sprint on on issue given certain conditions.

The rule is configured to set the sprint to the active sprint of a board (which is available in the dropdown for the Edit Issue -> Set Sprint action).

Screen Shot 2021-03-18 at 2.49.14 PM.png

The rule fails with the error:

No fields or field values to edit for issues (could be due to some field values not existing in a given project):

Screen Shot 2021-03-18 at 2.49.34 PM.png

Initially, this failure seemed to be only for one of our boards. Now, it fails for all boards. I can manually set the sprint to the active sprint for that board. There is only one active sprint on each of those boards.

Accepted answers

Brad_6guaep

Well I feel sheepish. This was due to a permission issue on the boards. The filter share was not allowing the Jira Automation user to inspect the active sprint.

The options to fix are to change the actor for the automation, or open the permissions for the board filters. In this case, we chose to share the board filters at the project level.

All comments

Bill Sheboy

Hi @Brad

Is this for an Issue Created trigger? If so, I wonder if this is related to the known race condition where the issue isn't fully available when the event is caught by the trigger.

If so, please try to add a Re-fetch action immediately after the trigger and before any other actions.

If not, would you please post an image of the complete rule where you are seeing this symptom? That may provide more context for the community to answer. Thanks!

Best regards,

Bill

Brad_6guaep

*deleted*

Brad_6guaep

Hi @Bill Sheboy , thanks for taking a look for me!

The trigger is on an issue transition. Here is the start of the rule. The failure is on steps such as the Edit Issue step you see selected. I can provide the rest of the issue if required, but it's quite long and just repeats the same pattern for many teams:

Screen Shot 2021-03-18 at 3.49.07 PM.png

Screen Shot 2021-03-18 at 3.49.27 PM.png

Screen Shot 2021-03-18 at 3.53.37 PM.png

Bill Sheboy

Thanks for that information, Brad.

First thing: branches are a bit slow in automation rules, even when they get in-lined. Consider replacing that structure of branching on the current triggering issue to use a long If/Else condition instead. Plus, the rule will be smaller.

Next, I see no condition on the issue type after the trigger, so I wonder if you are sometimes catching an issueType which normally doesn't set the Sprint field. Thoughts?

Next to confirm my understanding of the situation:

Is this a one-project rule, with multiple teams and boards, and sprints, or
Is this a global/multiple-project rule spanning the instance?

Brad_6guaep

Thanks for getting back to me. Great info around the branches, I will refactor for sure.

The trigger doesn't specify an issue type, but this particular transition is only applicable to standardIssueTypes, so we are good there. I've confirmed all instances of the error are happening on Story/Task issues, which have all these fields available.

The situation is #1. A one project rule, with multiple teams and boards and sprints. There is a 1:1 relationship from the boards in question for this rule to active sprints.

Brad_6guaep

Well I feel sheepish. This was due to a permission issue on the boards. The filter share was not allowing the Jira Automation user to inspect the active sprint.

The options to fix are to change the actor for the automation, or open the permissions for the board filters. In this case, we chose to share the board filters at the project level.

Bill Sheboy

Thanks, Brad, for sharing that information! That is a good symptom to watch for with automation. Odd error condition for a permission error.

__Bill

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