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 Chart" shows all issues as resolved, which is wrong

Henrik Schwarze

I use the "Created vs. Resolved Chart" in the project's summary. In this chart all issues are resolved, which is wrong. But when I go to the issues tab, two issues are unresolved, which is true. If I add a new issue, it is immediately shown as resolved in the chart, although I do not log any action with the issue. How do I configure issues, so that the chart is displayed correctly?

Accepted answers

Nic Brough -Adaptavist-

Could you check the actual resolution on the new issue?

I suspect your workflow has been set up to create issues with a resolution set, or the resolution has been put on the "create" screen so it's being set as the user creates it. If it actively says "unresolved" on the issue, then can you also nip into Admin -> Issues -> Resolutions and check that no-one has made the mistake of adding "unresolved" as a resolution (beacause that is very very bad)

All comments

Nic Brough -Adaptavist-

Could you check the actual resolution on the new issue?

Henrik Schwarze

Thank you. You're right. The resolution has been put on the "create" screen.

Nic Brough -Adaptavist-

I've seen a few like this recently while visiting people for work, hence the reasonably swift answer! Glad you found it and it's an easy one :-)

Ian McCormick_cytx7i

That seems to resolve the issues moving forward, but for those legacy tickets that already went through that flow, they are still stuck in the weird limbo of having Resolved, despite it being taken off the Create Screen.

Any thoughts?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

created-vs-resolved