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; } } }

How to mark issues as duplicate, stale, wontfix, etc.

mhulse

Today I found an issue on our board that was a duplicate of another issue in the backlog. I commented saying "this is a duplicate of FOO-22, closing". I dragged this issue to our "done" column.

What is the recommended way to mark issues as duplicate, stale, wontfix, etc.?

Just leaving a comment stating that the issue is a duplicate does not seem like the best solution.

I'd love some advice.

Accepted answers

Joe Pitt

We have resolutions of duplicate, wontfix, OBE (overcome by events), and can't reproduce to cover stuff like that.

All comments

Joe Pitt

We have resolutions of duplicate, wontfix, OBE (overcome by events), and can't reproduce to cover stuff like that.

mhulse

Interesting. Thanks for quick reply! So, the resolution feature is the best way to handle this? Do you have your resolution tied into a workflow, or do you manually pick a resolution when you move an issue around your board?

Joe Pitt

The resolution field should ONLY be shown on transitions because it is required when shown. I usually put a transition to closed from open to handle the the duplicate or won'tfix cases. The OBE and won'tfix reason are often used further into the workflow, usually from a status where research into the problem is being done. Or you can have it at the end and just run the issue through the workflow and close it with OBE or Won'tfix

mhulse

Great info! Looks like I need to dust of my workflow tweaking skills. laugh Last questions, does your workflow account for those rare occasions where you re-open an issue? It's been a while since I played with our workflows, so, I'm not sure if this would help me or not … But, are you able to share a screen shot of your workflow? No worries if that's asking too much, I totally understand … I just think it would help me to see the workflow in its graph form. Maybe you could add it to your answer? I'm sure other folks would also find it helpful to see a visual example. Again, no worries if that's not an option for you, I completely understand. Thanks a again, I really appreciate your pro help!!!!

Blair Gemmer_8ijhq8

Honestly what I did is create custom statuses for DUPLICATE and CANNOT REPRODUCE, etc and added them to my custom workflow.

Welcome!

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

Quick Links

Find more posts tagged with

issue

jira

cloud

jira-cloud

jira-core

workflow

resolution