"Won't do" resolution doesn't close the issue

[Jim Strange]

I have a state called Closed, and set a transition to this state, which sets status to DONE and has a post-function that sets the resolution field to "Won't do."

I've just noticed that an issue that was closed months ago keeps getting moved to the latest sprint (although not visible due to filter query).

This makes no sense. Why is a "DONE" status with a resolution of "Won't Do" being kept alive by Jira, and how do I correct this problem?

Thanks

[Negin Nafari]

Hi Jim, 

You can make an issue non editable by adding a property to the workflow status.

Here is a link to what I am referring to https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html

If this is not answering your question please add an screenshot of the related workflow

[Jim Strange]

Thanks, I don't want to make it non-editable. When I close it, I want it closed. I don't want it automatically moved to the next sprint when the current sprint completes. I've decided it won't be done, hence the resolution of "Won't do." It's over, not being done, will never be done. I want it to stay allocated to the sprint in which it was closed, the same way an issue does when its resolution is set to "resolved."

There's not much point in adding a screenshot, it wouldn't really tell you anything. I just want to know why setting an issue's resolution to "Won't do" means it keeps getting moved to the next sprint, and how I stop this unintuitive behaviour!

Currently I have a whole batch of issues which I assumed I'd closed, which Jira, for some unfathomable reason, seems to think should be kept alive and moved from sprint to sprint because it thinks they're not finished.

[Negin Nafari]

So basically this is happening only for the resolution "Won't do", and this wont happen if the resolution is for example "Done", correct?

[Jim Strange]

Yep, that's right. It seems as though Jira interprets "Won't do" as "might do next sprint."

Maybe I have to change all "Won't do" to "Resolved" to get round this bug. I'm not sure what Atlassian thinks the point of a "Won't Do" resolution is, if it doesn't mean "won't do." :-)

[Jim Strange]

FFS, it gets worse. If I accept that Jira thinks "Won't do" actually means "Will do later" and decide to change all those resolutions from "Won't Do" to "Resolved"..... Jira won't let me. Querying all the issues with a resolution of "Won't Do" then attempting a bulk update doesn't give me the option of changing the resolution field

So I'm stuck. Those issue will continue to be moved to the next sprint despite being in a status of "Done," and there seems to be nothing I can do about it.

[Negin Nafari]

Unfortunately there is no bulk change resolution. but here, in this documentation you can find how to figure this out by a little workaround.

https://confluence.atlassian.com/jirakb/howto-bulk-edit-resolution-321857142.html

If you are not able to add a public transition (so the users might use it), you can add a condition to the newly created transition to show the transition only to a specific group (or role)

[Negin Nafari]

btw you are mentioning to states "Closed" and "Done", and resolution "Done" and "Wont do".

Can you just check if both statuses "Closed" and "Done", are mapped in last right side column of the board?

[Jim Strange]

Yes, they're both mapped to Done. I resolved this in the end by changing the post-function to set Resolution to "Resolved" instead of "Won't do," then re-transitioning all the affected issues (from "Closed" to "Closed").

It's a bodge because "Won't Do" should actually MEAN "Won't Do..." but clearly in Atlassian's screwed-up world it means "Might Do." But yet again we have to work around the faults in Jira.

[Adam Shing]

I have the exact same issue now.  It's misleading or ambiguous if Won't Do doesn't mean the issue is canceled and shouldn't be revived.