Hello community! So I want to make a automation for jira to move every task that have TAG-Stat value equals "Cancelled" or "Completed" to Done section. But apparently there is some error with the automation Error message: * 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): If I surf in to the forum apparently it is because there is a restriction in the workflow. In the workflow I added restriction for the Done section for user not be able to move the ticket manually to Done because it is needed. Does anyone know how to fix this issue so the automation still can move the task to Done section if it meets the requirement? Thankyou

Hi @Thomas A and welcome to the community! You have two options: * Add the role atlassian-addons-project-access to the "allow these roles" on your restriction. This will grant the Automation user rights to the transition. * On your rule, change the actor to a a member of the Administrator role

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 Transition with Workflow Restriction

Thomas A_etqmp2

Hello community!

So I want to make a automation for jira to move every task that have TAG-Stat value equals "Cancelled" or "Completed" to Done section. But apparently there is some error with the automation
Error message:

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):

If I surf in to the forum apparently it is because there is a restriction in the workflow. In the workflow I added restriction for the Done section for user not be able to move the ticket manually to Done because it is needed.
Does anyone know how to fix this issue so the automation still can move the task to Done section if it meets the requirement? Thankyou

Accepted answers

Mark Segall

Hi @Thomas A and welcome to the community!

You have two options:

Add the role atlassian-addons-project-access to the "allow these roles" on your restriction. This will grant the Automation user rights to the transition.
On your rule, change the actor to a a member of the Administrator role

All comments

Mark Segall

Hi @Thomas A and welcome to the community!

You have two options:

Add the role atlassian-addons-project-access to the "allow these roles" on your restriction. This will grant the Automation user rights to the transition.
On your rule, change the actor to a a member of the Administrator role

Thomas A_etqmp2

Hello Mark thanks for the response. So for atlassian-addons-project-access is it already exist by default or do I need the Jira Admin to create the role?.
For the second option I already change the option for Admin only but seems the automtion does not have the same role as Admin in my Jira

Mark Segall

Based upon your response, implying that you're not a Jira Admin tells me that this is likely a Team Managed project and this may rule out option 1. That role is a standard role, but it only applies to Company Managed projects.

So, that leaves us with option 2. I would try setting the Rule Actor to your account. This will have the rule execute with your credentials. The only downside is that the issue history will always show that it's you making the transition.

Thomas A_etqmp2

Alright noted on that will try to figure out another work around for this case. Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

jira

workflow

automation

restriction

jira-work-management

unknown-hosting-type

jira-work-management-cloud