Kanban, best way to manage duplicates, wontfix, can't reproduce, won't do?

mhulse

I'm using a KanBan workflow.

Sometimes I encounter issues that are duplicates, outdated and no longer relevant, or I can no longer reproduce (to name a few).

Instead of deleting these issues, I want to move them into the "done" column and package them up with my release.

I ended up finding the "resolution" dropdown; I turned this on for my workflow and it has all the "markers" I want. Unfortunately, it's always required, and when I move it from my backlog to any other columns, it typically defaults to "fixed" and a line runs through the issue number:

Screenshot 2015-09-17 10.52.44.png

I just don't think I'm using the resolution dropdown in the way it was meant to be used.

Question:

How do I handle the above situation without using the "resolution" dropdown?

Optimally, I'd like to mark issues as "duplicate" or "can't reproduce" (etc.) and have my release notes organize these issues into groups.

Am I making any sense here? How do other people manage this?

Thanks!

Screenshot 2015-09-17 10.52.44.png

Jobin Kuruvilla [Adaptavist]

The resolution field should only be added in the last workflow transition. It should not be added on the edit screen.

Once you have the resolution field on the last workflow transition (Resolve, Close etc), you will forced to set it and you can pick the right resolution.

You can also have different transitions where a resolution is set in the post function. For example, you can have a transition for duplicates where the status is changed to Closed with a resolution 'Duplicate' set on the post function.