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

Error in Issue Transition Automation

Shaune Gilbert

I have an automation for parent issues with sub-tasks. If one of the sub-tasks is In Progress, then I want the parent issue to be In Progress. Below is the rule I'm using. Also, I know it's an if-else because I want to put together a more complex rule.

I think the problem is in my workflow -- see below.

The automation works when I'm transitioning from Queued to In Progress. However, if the parent is Under Review, the automation does not work.

The transition revision required (from Under Review to In Progress) has specific permissions (based on the project role) and brings up a screen where the user reassigns the issue and provides a comment.

I Imagine either the permissions or the screen in the Revision Required transition is causing the errors.

Is there a way to automate transitions like this or to fix this issue?

Error:

Action details:

["10013"]

Related issues condition

The following issues passed:

RDRT-67

Transition issue

Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status):

RDRT-67 (Under review - 10043)

If block

The following issues passed:

RDRT-69

Accepted answers

Joseph Chung Yin

@Shaune Gilbert -

What you need to do is to modify the your parent issue type's WF (which I believe you are already trying to do). Instead using the existing transition to the "In progress" status, you can create another transition with a different transition name to the same "In progress" status without the required validations as the existing transition.

In your automation rule transition issue status action, you will need to also enable "add regex to distinguish between multiple transitions to the same status" setup to use your new transition name to perform the action.

Lastly, I believe you should also correct your existing rule in the for For Parent rule, you should not need the if check for subtask condition. It should just be the status check of the parent issue. See example - (we are checking the parent issue for TO DO, so if it is in the TO DO status, then just transition the issue to IN PROGRESS)

Hope I understood your ask and my suggestion helps you.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

All comments

Joseph Chung Yin

@Shaune Gilbert -

Hope I understood your ask and my suggestion helps you.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Shaune Gilbert

Thanks for your answer.

Shaune Gilbert

@Joseph Chung Yin-- I created transitions from every status, which are named "Auto [status name]." Each of these transitions has one condition (Condition to hide a transition from the user. The transition can only be triggered from a workflow function or from REST) because I do not want users to be able to use these transitions.

Screenshot 2023-10-29 142718.png

I the automation rules run when I only have the "Auto [status name] transitions present in the workflow. However, when I add transitions with conditions/screens, I receive errors.

I assume this is a regex issue. If all my "hidden" transitions start with "Auto" (i.e., Auto in progress), then shouldn't the regex statement ^Auto* work? I'm new to regex, so I assume this is my issue.

Shaune Gilbert

@Joseph Chung Yindisregard that. My regex statement was wrong. ^Auto\s+.* worked. Thank you for your help

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management