You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I want to create an automation to change issues types and status if it's A to F.
I tried different composition, but I still have the same mistake.
- 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)
I tried to change issues types then the status or vice versa.
I have a company-managed project
Can you show us the Workflow diagrams for the two issue types? I want to see if there is a valid transition between "To Be Analysed" and "Accepted" for both issue types.
Is this rule scoped for a single project or multiple projects?
Yes, it's the both workflow diagram :
The first is the starting workflow and the second one we want them to go to. Today they are identical for the step, but we would like to reduce the first workflow to make the change between the two workflows. We were thinking about removing the Accepted step but maybe it wouldn’t be possible.
It's for multiple projects but on these workflows only.
Do you have Conditions applied to those that transition in those workflows that limits who can execute that transition?
If so, is the Actor specified in the Rule Details authorized to make that transition?
On the Rule Details page there is a field to specify the rule Actor. An example of this page is shown below.
What do you have specified in that field?
Is that user a member of the roles that are permitted to execute the transition?
I'm glad I could help.
If your questions have been answered and your problems solved by my responses, please consider clicking on the Accept Answer button.
I recommend not changing issue types using an automation rule.
Jira provides a specific UI function to "move" an issue between types, allowing the application to ask any questions necessary to resolve problems. And it will prevent some moves when they are not possible. Automation rules do not have this ability to stop and ask guiding questions to the user, and so the change may work (or fail) with no indication of what happened in the audit log.
Instead please consider cloning the issue in the rule to the new type, and then abandoning or deleting the source issue.