Closing as duplicate actually set resolution to "won't do" instead of Duplicate

[Bingzhou Huang]

I am pretty sure I did not mis click but the resolution is wrong. Please help. Thanks!

[Marc - Devoteam]

Hi @Bingzhou Huang 

As @Yash_reddy mentions, check the workflow transition, if you did and there is no post function on that transition doing this.

The other thing to check is the history tab, it might provide information. As their could be an automation rule doing this, so check those as well.

[Bingzhou Huang]

Checked that history already, it directly sets to "Won't do" which i did not select. Feels like a bug

[Marc - Devoteam]

Hi @Bingzhou Huang 

Can you show the history and the post function configuration of the used transistion

[Bingzhou Huang]

[Marc - Devoteam]

What is the config of the transition in the workflow from to do to cancelled

I can already tell you that on the transition a post-function is doing this, or do you have ther 3rd party aps in your instance, like;

JSU, JMWF or scriptrunner?

[Yash_reddy]

Hi @Bingzhou Huang 

Welcome to atlassian community 

Can you check  and see what resolution is set in the workflow step when closing the issue.

[Bingzhou Huang]

I checked, and even created test ticket to see. I set it to Duplicate but it ended up as Won't do. Thanks!

[Yash_reddy]

Do you have any automations that run after issue transitioned. Can you check issue history to see if it's changing the resolution after you set it.

[Bingzhou Huang]

Also checked that history already, it directly sets to "Won't do" which i did not select. Feels like a bug

[Yash_reddy]

Which user is setting to "won't do" is it Automation?

[Bingzhou Huang]

[Yash_reddy]

I believe it's setting from workflow postfunction. Please check if there is anything setting in the transition from ToDo to Cancelled