Issues remain Unresolved after trigger

[Paula Manildi]

We have add a trigger for a merge operation to move an issue from In Progress to Resolved (Works Great). But...

1) the resolution date doesn't' get set

2) there is no Resolution (i.e., we can't pre-populate "Done" or "Fixed/Completed" into the Resolution field, so it remains Unresolved.

I can fix 1) in the workflow but not 2 without creating a special transition Is that what people are doing?

[Earl McCutcheon]

Hi Paula,

To populate the resolution you can add in a post function on the transition to the resolved status to get the value to populate using the "Update Issue Field" post function.  The Resolution Date will be populated when the resolution field is set but you only have a single value to add in.

If you want to be able to manually choose a different value on the resolution screen with one transition, but have a forced default value on the workflow trigger, you could set up a unique transition for this using the "Update Issue Field" post function to be used by your workflow trigger.  This would give you the option to have the value set one of the two transitions.  This method would achieve an option for you but both transitions would be visible.

A method you could use to clean this up a bit would be to use the add-on ScriptRunner which has a "Hide transition from user" Condition that can be applied on the workflow level so that only the workflow trigger could execute the special transition and users logged into the instance could manually resolve issues as needed.

Regards,
Earl