Automation throwing error on setting resolution
Asked by Jill Vieregge:

Slightly different than what I've seen in the community so far.

#1: My automation: if a parent is done set its children to done and inherit the resolution reason from the parent.

#2: automation error

#3a: shows the workflow. For global transitions to Canceled/Done, has a trigger that sets the resolution.

#3b: For Reset Resolution, has a screen that includes the resolution.![1. Automation.png](/t5/image/serverpage/image-id/333556i5AE7B366316C76B1/image-size/large?v=v2&px=999 "1. Automation.png")![2. Automation Error.png](/t5/image/serverpage/image-id/333555i2FF161F03954E4D7/image-size/large?v=v2&px=999 "2. Automation Error.png")![3a. Wkflow global transition.png](/t5/image/serverpage/image-id/333558iF9BD6C77CF45DFBE/image-size/large?v=v2&px=999 "3a. Wkflow global transition.png")![3b. Wkflow Reset Resolution.png](/t5/image/serverpage/image-id/333557iE329A51BBC318587/image-size/large?v=v2&px=999 "3b. Wkflow Reset Resolution.png")


Answers:
author: John Funk
body: Hi Jill,

The problem is probably that you are trying to set a value on the transition but there is a screen associated with the transition, so the automation doesn't know what to do with that.

comments: author: John Funk
body: [@Jill Vieregge](/t5/user/viewprofilepage/user-id/4540914) - Did you actually publish the workflow after you removed the screen?

Here's another suggestion - add a new transition to Done - call it System Update or something like that. Then add a Condition to the transition User is in any Group.

Select atlassian-addons-admin group. You can also select the Jira Admins group if you want.

Save and Publish the workflow. Then test again.


author: Jehan Bhathena
body: Hi [@Jill Vieregge](/t5/user/viewprofilepage/user-id/4540914) ,

I'll agree with what [@John Funk](/t5/user/viewprofilepage/user-id/7148) mentioned, you seem to have a Screen present on the 'Reset Resolution' transition, does this screen have anything mandatory? Also, is the Resolution field include in this screen?

Another possibility (this is in theory), the parent itself may now have a resolution?(To debug this ppoint, try using Log Action to print the parent tickets resolution to verify it has a value)

comments: author: Jill Vieregge
body: I removed the reset resolution transitions (with screens).

Added logging.

But get the same error.

Also, although the automation logging ends with saying the does not move transition, its status and resolution is in fact changed to reflect the parent which is the desired behaviour (status = Canceled and Resolution = Canceled).![Auto w Logging.png](https://community.atlassian.com/t5/image/serverpage/image-id/333731i4019BD040178E327/image-size/large?v=v2&px=999 "Auto w Logging.png")![Logs.png](https://community.atlassian.com/t5/image/serverpage/image-id/333730iD274B5B48DAB5043/image-size/large?v=v2&px=999 "Logs.png")

Jehan - the parent is supposed to have a resolution. The children are supposed to inherit it from the parent.


author: Jehan Bhathena
body: Hi [@Jill Vieregge](/t5/user/viewprofilepage/user-id/4540914)Vieregge,

About the "Reset Resolution" Transition, what I meant was that the screen should have the "Resolution" Field available, unless it is available there Jira won't allow resolution to be set for that transition.


Tags: cloud

jira-cloud