How to change Resolution status with Jira Automation rule?

[Irina_Bel_Stiltsoft_]

Community, please, help!

The case is simple: when the issue goes to status Done, but somebody comments on it, we want to make a transition to In Progress status via automation rule. But a blocker is that when the issue transits into Done, it receives the Fixed resolution, which makes it impossible to use the Jira automation rule with changing statuses. Is there a workaround to this?

[Rilwan Ahmed]

Hi @Irina_Bel_Stiltsoft_ ,

For the workflow  transition from Done to In-Progress, add a post function "Clear Field Value" and select Resolution. This will clear the resolution field value when a ticket is transitioned back to In-progress by automation or by user manually . 

(Updated the Typo errors)

[Irina_Bel_Stiltsoft_]

@Rilwan Ahmed Thank you, I appreciate your answer. The thing is that when I manually do this to In progress, Resolution disappears. It is only an obstacle for the automation rule.

[John Funk]

Yep, this is the thing to do. 

[Rilwan Ahmed]

Hi @Irina_Bel_Stiltsoft_ 

Please check below points and let me know. 

1. Does your workflow has two different transitions from Done to In-Progress ?
2. Does the automation rule actor/User has the edit permission the tickets ?
3. Is there any Workflow transition properties  or Status properties added ? 

[Bill Sheboy]

Hi @Irina_Bel_Stiltsoft_ 

Has this rule been copied from another project?  Specifically, from a company-managed project (CMP) to team-managed project (TMP), from TMP to CMP, or from one TMP to another TMP?

If so, I suspect the rule has saved values for the status id values and those are incompatible/different from the new project.

The fix for this is to edit the rule, delete the transition action, and re-add it.  The new saved values for status should be correct for the project.

Kind regards,
Bill

[Tansu Akdeniz]

The root cause could be different than resolution field. What about the rule actor? This person may have a lack of permission for this transition.

[Irina_Bel_Stiltsoft_]

@Tansu Akdeniz 

Thank you for your reply. I see it in the rule logs (on the screenshot). It says the Destination status couldn't be resolved. And this rule on other projects where there's no resolution in the workflow works well.

[__ Jimi Wikman]

Are you sure it is the resolution that causes this? It might be the fact that there is no transition from closed to in progress?

I usually add a post function in the workflow that remove the resolution when a transition occur from the closed status. Perhaps that would help your case as well?

[Irina_Bel_Stiltsoft_]

@__ Jimi Wikman Thank you for your professional input. As I've mentioned in the previous answers, I see the reason in the automation rule's logs (on the screenshot). It says the Destination status couldn't be resolved. And this rule on other projects where there's no resolution in the workflow works well.

Regarding the post function, I see it works well when I manually transit the issue to the In Progress status again. There's no resolution. But for the Jira automation rule, it's an obstacle.

[__ Jimi Wikman]

Usually when you get the error that a status can not be resolved, then it means that the actor does not have permission to do the transition, which you have ruled out.

If you compare the two projects where one works and one does not, do they have any differences or are they the same? Especially look at project roles, Permissions and Security.

If it works in one project and not the other, then it is something on project level...