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 when reopening ticket to "Waiting for support"

hasancansaral

I have the following rule:

But it fails with:

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

XX-35 (Resolved - 5)

I want to re-open the issue with "Waiting for Support" status. What am I doing wrong?

Accepted answers

Paul Wiggers

Hello @hasancansaral

This sounds like your workflow does not allow a transition from Resolved, Closed or Canceled, back to Waiting for Support.

Could you share a screenshot of your workflow diagram?

In addition, it might be that the properties of the Resolved, Closed or Canceled issues, prevent you from editing the issue. Could you check if those statuses have properties set and if so, what properties?

The last option, is that there is a restriction on who can trigger the transition. Please check the Conditions of the transition in your workflow.

All comments

Paul Wiggers

Hello @hasancansaral

This sounds like your workflow does not allow a transition from Resolved, Closed or Canceled, back to Waiting for Support.

Could you share a screenshot of your workflow diagram?

The last option, is that there is a restriction on who can trigger the transition. Please check the Conditions of the transition in your workflow.

Trudy P Claspill

Hello @hasancansaral

Welcome to the Atlassian community!

Have you change to project to which this rule applies (the Rule Scope) since you set up the step to select the Waiting for Support status? If so, please try reselecting the status in that step. Or try deleting that step and re-adding it.

Do all the issues that might trigger this rule include in their Workflows a valid transition from Resolved, Closed, and Cancelled to Waiting for Support?

Who is the Actor for the Rule? Does the Actor have sufficient permissions to make that status change in that project?

hasancansaral

@Paul Wiggers Thank you for your response. I've updated the workflow and created a path from Resolved to Waiting for support. The rule now partially works, the issue status is transitioned to Waiting for support but it it not listed in Open issues. I thought that it may be because I'm not clearing its Resolution field and tried to clear it with:

Screenshot 2023-04-06 160109.jpg

But this time I get:

Unknown fields set during transition. Field may not be on transition screen. Fields ignored - Resolution (resolution)

hasancansaral

@Trudy P Claspill Thank you for your response. I've successfully managed to transition the issue to Waiting for support, however, the issue is not listed in Open issues after being transitioned to Waiting for support. Could you look at my other comment?

Paul Wiggers

Hello @hasancansaral

Good to hear that the transition is now working.

The easiest way to clear the resolution is to, once again, edit your workflow.

Select the transition > Select Post Functions on the right > add a post function > Clear Field Value > Select Resolution

That way, whenever the transition is used, the resolution will be cleared. You can then remove the action from the automation since the transition will take care of it.

hasancansaral

@Paul Wiggers I've also managed to clear Resolution with Edit Issue action:

Screenshot 2023-04-06 165533.jpg

However, Transition issue to Waiting for support emails me every time. To overcome this, I removed Transition issue action and tried to add "status": "Waiting for support" to Edit issue fields. This time I got:

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

How do I stop Jira Automation from emailing me every time the issue is transitioned?

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