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

Created vs Resolved Issues Report

Resignola, Kelly

Hello,

I have done some research on this report and determined that it considered issues resolved when the Resolutions field is populated. Is this correct?

I've also read the the Resolutions field can be configured to add values such as Done (see below). If I add Done, will this report count all issues with a Done status as a Resolved issue?

Accepted answers

Mikael Sandberg

Hi @Resignola, Kelly,

Welcome to Atlassian Community!

You are correct, the created vs resolved report is based on the resolution field. And no, adding a Done resolution will not automatically make all issues in the Done status marked as resolved, you would still have to set the resolution when transitioning to Done. This can be done either by adding a post function in the workflow that sets the resolution field, or by adding the resolution to a screen and associate that screen to the transition to done.

All comments

Mikael Sandberg

Hi @Resignola, Kelly,

Welcome to Atlassian Community!

Trudy P Claspill

Adding to this...

Using a Post Function or a transition screen applies only to Company Managed projects.

Note also that you should have Post Functions on your transitions to not-green/not-done statuses to clear the Resolution field also. Otherwise if an issue goes from Done to In Progress, those reports would still count the issue as Resolved.

If you have a Team Managed project you don't get to customize the values for the Resolution field. An issue transitioned to a green/done status should automatically get the Resolution field set to Done.

And if you are working with Work Management projects, those project DON'T set the Resolution field. For a Company Managed Work Management project you can use the Post Function option, but that is not available if your Work Management function is Team Managed.

If you need more information on any of the above, let us know.

Resignola, Kelly

Thank you @Mikael Sandberg and @Trudy P Claspill

Upon further investigation, there are some issues that are being counted as Resolved that have a Done status. Below is the workflow. We haven't applied Post Functions. Any idea how these issues got the resolution field set?

BTW, our Jira tenant is administered by our Corporate tech support team.

Issues with Resolution field set to "Done":

Workflow:

Trudy P Claspill

The Resolution field was likely set for those issues during some transition they went through, and not been cleared when it should've been.

When a project is initially created the workflow is set based on the template used. In the default workflows that Jira uses the setting of the Resolution field on the transition to the Done status is often automatically included, but the clearing of the field on transitions to other statuses is not. And if additional green/Done statuses are added to a workflow, Jira doesn't automatically include setting the Resolution field for transitions to those statuses.

You Jira Administrators will need to examine each workflow transition and ensure they include Post functions to set the Resolution when transitioning to a green/done status, and clear the Resolution for all other transitions.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

report

created-vs-resolved