NEED Help - Asked this a few times and not able to get an answer on Done

[Lisa Besteni]

I've been trying to understand how JIRA reporting and gadgets work.

My company would like to be able to pull all reporting from standard JIRA reports (e.g. burndown charts, velocity charts, etc.) as well as from JIRA gadgets (heath check, created vs resolved, etc.).

Some of our squads use statues liked "Staging" or "Merged" to indicate the status of a card before it's pushed to Production . These statuses are for cards that are Dev and manual QA complete but still need to go through automation testing. We want to be able to see progress during a sprint via reports and gadgets. 

Is it true that unless the status is "Done" the reporting won't recognize the card as done? I've tried 1) putting the "Staging" and "Merged" statuses in a resolved state, and 2) placing them in the last column on the board, but I still don't think the reporting recognizes them as Done.  

Can someone let me know so we can help our teams. Thank you.

[Nic Brough -Adaptavist-]

This is probably worth following up on the question that has an answer marked correct - where are you stuck on that answer? 

https://community.atlassian.com/t5/Jira-Software-questions/Do-Jira-Reports-only-acknowledge-the-Done-status/qaq-p/1947949

[Walter Buggenhout]

Hi @Lisa Besteni,

There's 2 important things here: for standard reports linked to a Jira board, issues are considered complete when they are in the rightmost column of that board.

Apart from that, Jira uses the resolution to distinguish between open and completed issues. Issues having a value in the resolution field are considered completed, while all the others are open, regardless of their status.

Hope this helps!

[Joseph Chung Yin]

@Lisa Besteni -

From issue point of view, the key element is the Resolution field.  If it is not populated (default is always showing as "Unresolved" which it is actually a null value representation of the field), then it is not considered as completed.  This is regardless of statuses assignment.

From the boards point of view, the right most column (the last column on the right - default is colored in GREEN), it represents the terminal state of an issue.  Example - In a SCRUM board, if issue is located at that column even if it is not completed in an active sprint, it will be dropped when one completes a sprint.  The system will not prompt you if you want to move it to the backlog or for other upcoming sprint assignments.  Thus, it is important that the WF status placed under the column needs to have the resolution field populated (during the issue transition's postfunction to the terminal status)

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.