Set Resolution in automatic merge trigger versus manual transition

[Daren Scott]

If I have an automatic trigger on a transition between issue status's (like In Review to Closed for example) for Pull request merged, no resolution gets set for that issue.  I could add a post function and set the resolution to Done which fixes that problem, but what about an issue that cycles through the workflow without a pull request merged?  If I wanted to manually set the resolution to Won't Do via the default resolution transition screen, it then gets set to Done because of that post function.

It seems like this would be a common case, but I can't find any information about it.  Any thoughts are appreciated.

[Jack Brickey · Accepted solution]

I would create two different transitions: one for the automated pull and one for the manual. I would require the user (manual transition) to select the proper Resolution value. As you said for the automated transition I would use a Post Function to set to Done. Now don't forget to clear the Resolution if you ever transition back out of Done/Closed.

[Daren Scott]

Is there a way then to "hide" the transition button that would be used for the automated one?  Such that the user would not see it or be able to use it as one of the available workflow transition buttons on the single issue page.  I guess that's not a huge deal but it wouldn't be very intuitive if there was two buttons that did virtually the same thing from outward appearances.

[Jack Brickey]

u betcha! edit the transition and add the following Condition to it.

Hide From User Condition - Condition to hide a transition from the user. The transition can only be triggered from a workflow function or from REST.

[Daren Scott]

Awesome.  Thanks Jack!