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

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.


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?


2 answers

1 accepted

1 votes

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.

(I had to wait 24 hours until I could post this reply due to my status … Sorry for the late comment) … Thank you Jobin! I really appreciate the help. I'm going to read the docs about transitions and workflows. I'm still pretty new to Jira, so I'm not as versed as I would like to be on these topics. I know the docs are robust though, so I'll start there and come back to the forums if I have more questions. Thanks again! +1

1 votes
Joe Pitt Community Champion Sep 17, 2015

the resolution is always required when presented on the screen. The normal practice is to ONLY put it on a screen you use in the transition where you want to resolve/close the the issue.

Thank you for the reply Joe! I really appreciate it. I am not so familiar with transitions and how to manage them. But this gives me keywords to use when searching the docs. Thanks so much for the help! +1

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,826 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot