Resolution: Setting and unsetting

[Deleted user]

If the resolution field is set, for example: to "Done", is it possible to unset/reset the resolution field back to "Unresolved" if an issue is reopened?

[Joe Pitt · Accepted solution]

you need to pass it through a transition that CLEARS the field in a post function. An example is the out of the box workflow does that from closed to reopened. 

[Deleted user]

Joe, thanks. 

I was trying to manually unset it but now see I should do exactly what you suggest.   

Sign me, "Learning JIRA the hard way . . .learning as I go"

Jim

[Joe Pitt · Accepted solution]

@[deleted] since you're new here is an issue that causes lots of folks grief and is painful to fix if you've been using JIRA long.

Do not delete issues. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. Deleting issues will come back and bite you when it is the most inconvenient. I suggest closing with a resolution value of Deleted anything you want to delete. I implement a special transition only the project lead can execute and it requires filling in a reason field from a select list (such as entered in error, OBE, Duplicate, Other) and explanation text.

. Missing issue numbers will eventually cause a question about what it was and why was it deleted even if it was done properly. Missing data always brings in the question of people hiding something that may have looked bad.

The only viable way to restore an issue is to create a new instance of JIRA and restore a backup that has the issues. Then export them to a csv file and import them to your production instance. You will lose the history.

Also, don't delete users. Move them to inactive. Deleting users will cause SQL errors. JIRA stores a pointer to the user id wherever it is displayed, not the text name. Deleting the user will cause JIRA to try to resolve the now obsolete pointer contained in the user field. Also, by deleting users you destroy the data integrity of the issue. 

[Deleted user]

OMG . . . and I thought ClearQuest was painful . . . LOL

Thanks for the heads up, Joe.  I'm printing this and hanging  it on the wall for everyone to see.

[Deleted user]

BTW: You also don't want missing issue numbers if you are working with the government as they require all changes be accounted for with supporting data (who, what, where, when, why and how)

note: of course there are exceptions - but I believe it is better to keep everything