nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Jim Strange_uuicuk

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

Accepted answers

All comments

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_uuicuk

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_uuicuk

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." :-)

Adam Shing_d53nfo

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud