Why are some gadgets depending on status of Resolved?

[Brian]

We are struggling to understand and use Jira's Gadgets in the dashboard. The workflow for stories does not include "resolved" and yet it is in a default Gadget that does not represent. Is this Gadget junk or are default workflows in Jira Cloud missing assumed states?

[Jack Brickey]

resolved is a generic word. I can't be sure whether resolved here equates simply to your done status OR if it is associated with the Resolution being set. It should be pretty easy to test this out. Given that you are showing 0 of xx issues resolved my suspicion is that it is associated with Resolution being set and I suspect you are not setting the Resolution when you move the issue to your 'done' status.

[Brian]

Thanks. We are setting to check the box for resolution but it still does not seem to affect the current issues. Will changes to this only affect new items?

[Nic Brough -Adaptavist-]

Yes, the tick box you mention actually equates to having a workflow post-function that sets a resolution.  So an issue has to go through the transition to get the resolution set by it.  It's not a function of the status or column.

[Jack Brickey]

and if you want the closed issues to be counted you would need to re-transition them. there are some ways to deal w/ this other than reopening them if you really want to go that path.

[Brian]

OK, so maybe a silly question but if the Resolved status does not exist in the workflow, will I need to add this to it with all issues able to transition to this status?

[Nic Brough -Adaptavist-]

Ah, hang on, no.

There are two things Jira might be looking at when asking the question "is it open?".  Neither of them are the status (directly)

Jira Software mostly considers an issue "done" when it is in the last column on the board (columns represent status, so it is looking at status indirectly.  But you can put any status you want in the last column)

Everything else looks at the Resolution field, not status.  If the resolution has a value set, the issue is resolved.  If the resolution field is empty, the issue is open.

So, no, you do not need a Resolved status.  You need to consider the resolution field.

As well as the last column.  Ideally, get them in lockstep - issues going into the last column get their resolution set, issues moving out get it cleared.

[Jack Brickey]

this isn't about a "Resolved status" it is about the "Resolution" field. You can have one or many 'done category' statuses (Closed, Done, Cancelled, etc.). For each transition into the various 'done category' statues you should set the Resolution field. This can be done via a simple Post Function and set the resolution to say "Done" or you can add a screen to the transition and set up a Validator so that the user triggering the transition can select a resolution value (Done, Won't do, Cancelled, Cannot reproduce, etc.).