Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,369
Community Members
 
Community Events
175
Community Groups

Transition destination status not resolved

I'm using automation to try to transition an issue to the next status in a workflow. I have a screen for all status transitions, with the minimum being just a comment screen if no other information is required.

So first question is ... if a transition has a screen then will that stop my automation working?

I suspected it might so I created an "All" transition to the status I want to go to, without a screen and renamed it to "Auto". Then I set the transition match in Automation to ".*uto.*" (without the quotes) ... but I get the below message.

Any tips or advice would be gratefully received.

Thanks Mark

 

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):REL-376 (Submitted - 10177)

1 answer

0 votes
nmenere Atlassian Team Sep 13, 2020

Hi Mark,

Did you get this working?

Screens wont affect whether transitions as fields aren't required (except Resolution when used).

Is this a next-gen project in Cloud? We have recently made this a lot easier to specify Statuses and no longer show duplicate names.

A screen shot of your rule will help see what is going on.

 

Cheers,
Nick

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events