In the report "Created vs. Resolved Issues Report" what is the criteria used for Resolved?

[David Goldstein]

My report never shows resolved issues. What constitutes Resolved? How does the report know what my workflow means?

[Nic Brough -Adaptavist-]

An issue in Jira is "resolved" when the field "resolution" has a value set

Nnote - it is any value, doesn't matter what it is.  You could have done, won't fix, ended, fixed, penguin, unresolved as options, all mean "issue is resolved".  The only content that means "unresolved" to Jira is <null>, and it displays "unresolved" for you when it has a null in the database.

Your workflow needs to inform Jira here.  Simple rules are that it needs to set a resolution as issues close (either by putting the field in front of the user as they close, or by a post-function on the transition), and clear it on re-open (again, with a transition post-function)

[David Goldstein]

thanks

[David Goldstein]

So in order to get the use of some (many) of the reports I need a field called Resolved in my project -- is that right? If so, I do not have such a field -- how do I add it to an existing project and get it to be set and cleared as issued are closed and reopened?

[Nic Brough -Adaptavist-]

No.  You need the built-in field called "resolution" to be used. 

It's always there, but I would guess that you have removed it from screens and/or used the field configuration to hide it.  It's fine to hide it, but if you do, you *must* set it with post-functions at the very least, to enable Jira to know when things are done.