Sprint reports not showing completed work
Asked by tim-vandijck:

Hi there,

We've recently started working with sprints in our Jira environment. However, we've not been able to get any value out of the reports available such as the Burnup report, as no issues are being identified as completed work.

![Screenshot 2024-07-25 at 14.33.54.png](https://community.atlassian.com/t5/image/serverpage/image-id/337908i3A58A24E296F7B0E/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 14.33.54.png")

Reading through the forum, I've found that the reason for this is because the issues that are done are not set to the utmost-right column on the board. Our workflow is currently as follows on the board:

**To do \> In development \> Review QA \> Done \>** **Released**.

We like to save up features before releasing them, but this will prevent the sprint reports from generating any useful data.

Could anyone advise me how to handle this better in Jira? A way that will ensure we get value out of the reports and are actually able to calculate our velocity, without losing track of what's currently released to the public and what's not?

Any help on this would be much appreciated!


Answers:
author: Bill Sheboy
body: Hi [@tim-vandijck](/t5/user/viewprofilepage/user-id/3544563)

As you noted in your original question, Jira Scrum boards detect completed work in a sprint (for burn charts and other reporting) when the issue is in a status mapped to the rightmost column on the board.

Your team appears to track releases separate from the sprint work...and you note using a Team-managed project.

You could do that using versions (with the Fix Version field) and release when needed, rather than having a separate status value.

Kind regards,  
Bill

comments: author: tim-vandijck
body: Hi Bill thanks for your answer,

You make a good point - perhaps it would be wise to get rid of the released status value. However, If I'm not mistaken, issues are removed from the board/backlog when they are set to the rightmost column on the board after 14 days or so.

I'm afraid to lose track of done issues unless they are added to a fix version.

Happy to hear your thoughts on this, thanks again.


author: tim-vandijck
body: For now, I've gone with the workaround explained here;

<https://jira.atlassian.com/browse/JSWCLOUD-21257>

We'll indeed get rid of the Released column, and have written a query with a shortcut that returns all issues in the project that have been done for more than 14 days, to not lose sight of done issues.

Thanks for your help!


author: Bill Sheboy
body: That is a good method for the Kanban boards. For Scrum board, the issues are out of view for the board when the sprint completes (and the next one starts). In that case, the Versions page is one location to see the status of the issues for a specific version.


author: Anandhi Arumugam
body: Hi [@tim-vandijck](/t5/user/viewprofilepage/user-id/3544563) Please check if a resolution is set on the issues moved to the 'Done' status. Only when a resolution is set, these reports will be able to pull issues based on the Resolved Date. Hope this helps.

comments: author: tim-vandijck
body: The thing is, it looks like there is already a resolution set for the issues moved to done. I see a checkmark behind the done column.![Screenshot 2024-07-25 at 15.51.45.png](https://community.atlassian.com/t5/image/serverpage/image-id/337922i0D19026DE1EFE5D3/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 15.51.45.png")![Screenshot 2024-07-25 at 15.51.56.png](https://community.atlassian.com/t5/image/serverpage/image-id/337921iD0AC0447E4AFD339/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 15.51.56.png")


author: Anandhi Arumugam
body: Can you see if the Resolution Date set on these issues? You should see something like this.

![Resolved Date.png](https://community.atlassian.com/t5/image/serverpage/image-id/337924iC19584B8AD5B245E/image-dimensions/257x201?v=v2 "Resolved Date.png")


author: tim-vandijck
body: Yes, in this case I have one issue in 'Done' but it isn't seen as a completed issue in the reports. ![Screenshot 2024-07-25 at 16.02.09.png](https://community.atlassian.com/t5/image/serverpage/image-id/337925i95B381A85D7777A1/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 16.02.09.png")


author: tim-vandijck
body: Is it worth noting this is a team-managed project? As it feels like certain settings behave different for these type of projects..


author: Anandhi Arumugam
body: That's useful info. Can you try this?

Edit the workflow, go to the transition coming into the Released stats and add a workflow property below.

![Workfloe Transition Property for Resolved status.png](https://community.atlassian.com/t5/image/serverpage/image-id/337968i48C25D4BBDED23D9/image-dimensions/447x243?v=v2 "Workfloe Transition Property for Resolved status.png")


author: tim-vandijck
body: I've done as you indicated, what would this do?

![Screenshot 2024-07-25 at 17.28.49.png](https://community.atlassian.com/t5/image/serverpage/image-id/337970i874B113C517372AA/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 17.28.49.png")


author: Anandhi Arumugam
body: yes, that should work.


author: tim-vandijck
body: I'm afraid it's not changing anything in the reports. Still no completed work this sprint (whilst 1 issue is currently done)


author: Anandhi Arumugam
body: The issue should be in Released status to be able to show up on the reports.


Tags: cloud

jira-cloud