How can/should I use the other resolution fields

[Will Henry]

I would like our team to start using the Cannot Reproduce resolution field on bug issues when there are reported bugs that cannot be reproduced.

These are my ideas:

1. Create/update the transition to the Done status, in our workflow for bugs, so that it uses a screen that allows them to set the resolution.

2. Create a new status, in our workflow, called 'Cannot Reproduce', add a transition to this status that uses a post function to set the Resolution field to Cannot Reproduce. Add this status to our 'Done' column on our Knaban board.

Is there a preferred method?

[Nic Brough -Adaptavist-]

Hi Will, 

Using other fields for resolution will not work.  Jira looks only at the system resolution field, adding your own custom resolution field is of no use.

You should always do what you suggest in option 1, if you have a situation where an issue might be resolved with different resolutions.  Obviously, make sure there is a "cannot reproduce" option in the system resolution field.

For option 2, mmm, probably not.  Do you really need a whole status to tell people that an issue was resolved as "cannot reproduce" a second time?  Do you need to report on "status = cannot-reproduce and resolution = cannot-reproduce"?  What happens when people create a mismatch (status = cannot reproducte but resolution = done / closed / not a bug / etc"?  I would stick to "issue is closed, the resolution is a general flag to tell you why it needs no more work - fixed, can't reproduce, development done, duplicate, etc"

But absolutely yes about having a transition that makes it easier for your people - a transition to done/ended/closed that is labelled "cannot reproduce" and sets the resolution for them is nicer than shoving them through a screen and asking them to choose the right resolution every time.  It is very common to see this, and similarly, "duplicate" transitions.