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 - unsetting resolved field

Luke Wirth

I have been researching the Created vs Resolved issues report and it appears an issue is resolved when the Resolutions field is populated - with any option, even "none". Is this correct?

If so, is there a way to unset the Resolution field so that an issue then is not classified as Resolved and therefore does not show in the report as such.

Accepted answers

Mikael Sandberg

Correct, if the resolution field has a value Jira consider the issue as resolved. None is not an option unless you have created a resolution with that name, which is not recommended. Here is a good KB about best practices for resolution. It also tells you how to clear the resolution. What is not mentioned in the KB is that you can use an automation to clear it, you can either create a manual triggered one or a scheduled one to clear the resolution.

All comments

Mikael Sandberg

Danut M _StonikByte_

Hi @Luke Wirth,

O solution would be to clear the Resolution field or not set it, unless the issue is really resolved. You can do this by altering the transitions fork your workflow.

Another solution, would be to use a reported vs done gadget that does not use the resolution field.

Our Great Gadgets app offers a gadget that uses the issue statuses instead of Resolution. See this article: https://community.atlassian.com/t5/App-Central/A-powerful-Reported-vs-Done-chart-for-Jira-dashboards/ba-p/2610902

Or, even better, you could use the Cumulative Flow Diagram (CFD) gadget offered by the same app. See https://community.atlassian.com/t5/Jira-Software-articles/Building-a-powerful-Kanban-dashboard-in-Jira-with-Great-Gadgets/ba-p/1664331

Hope this helps.

Danut

Luke Wirth

Hi @Mikael Sandberg thank you for this. The KB was a good read, unfortunately in our live environment our admins prevent the use of Post Functions, so this is not an option.

I have tried to use Automation and setting the Additional Field to:

{
"fields": {
"Resolution": ""
}
}

Within the Edit Issue action, but this does not seem to work, and simply errors when running with a "Could not find valid 'id' or 'name' in resolution object. (resolution)" error. I assume this may be because the Resolution field has a pre-defined set of options of which 'blank' or 'null' is not one so may be within our set up unsetting is not an option.

Does that make sense?

Mikael Sandberg

Use this to clear the resolution field

{
&nbsp; "fields": {
&nbsp; &nbsp; "Resolution": null
&nbsp; }
}

Luke Wirth

Thank you!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-cloud

jira-server