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

Destination status could not be resolved

Pavel Bokov

Hello,

I have the following automation configured:

My goal is, when an Issue1 in Project1 is moved to a different status, all issues in Project2 related to Issue1 are moved to the same status.

This is my Issue1:

It has "relates to" = Issue2.

I want, when I move Issue1 to IN PROGRESS (for example), Issue2 to get to IN PROGRESS as well.

My workflow for Project1 allows ANY STATUS -> IN PROGRESS.

My Workflow for Project2 allows ANY STATUS -> IN PROGRESS as well.

For some reason, when I transition Issue1 to IN PROGRESS, I get an error in my automation

So far I can't understand what is causing this. Please help.

Thank you

Accepted answers

Joseph Chung Yin

@Pavel Bokov -

I concurred with what @Trudy P Claspill / @Jehan Bhathena suggested, instead of using your existing logic "Copy from triggering issue" setup, you can just set the destination status to "In Progress" Example -

Unless you have a specific reasoning to copy from the triggering issue.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

All comments

Jehan Bhathena

Hi @Pavel Bokov ,

for debugging check if you can transition the workflow for both tickets manually.

If your usecase is limited to moving ticket to in progress, would suggest trying the Status Hardcoded to "In Progress" Directly instead of the dynamic value you've used currently.

Trudy P Claspill

Hello @Pavel Bokov

Based on the screen images you provided both projects are Team Managed projects. Is that correct? You can see the project type at the bottom of the panel on the left when viewing each project.

If so, I don't have a solution for you but I can explain what is happening.

Even though the projects may use statuses that have the same names, they are actually considered different statuses in the back end and you can't use the Copy From Trigger Issue option.

I have tried two different options using the name of the Status from the trigger issue, neither of which worked.

I tried using a smart value in the Transition action.

Screen Shot 2023-08-25 at 1.25.18 PM.png

Though the target issue does have a valid transition available to a status named the same (In Progress) I still get this error:

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):
TKA-10 (To Do - 10003)

I tried using an Edit action and JSON to set the Status value

Screen Shot 2023-08-25 at 1.29.17 PM.png

But I got this error:

Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -

Status (status)

Joseph Chung Yin

@Pavel Bokov -

Unless you have a specific reasoning to copy from the triggering issue.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Pavel Bokov

Thanks, @Joseph Chung Yin , I went ahead with explicit destination status definition and it worked fine, though my script is much longer now, but it is a one time job.

Pavel Bokov

Thanks, @Trudy P Claspill for deeper analysis of the issue and good explanation of what might be happening. This makes sense. I solved my issue by explicitly defining the destination statuses based on source.

Pavel Bokov

Hi, @Jehan Bhathena, yes this was tested before creating the ticket. I was able to resolved the issues based on the other answers. Thanks

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