You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi all,
even if I checked several answers in the community I still do not understand what's wrong with our board.
Problem
Solved issues are not shown as completet in the sprint report
Our situation
Our workflow columns have the status "ticket closed" in the right column. Once I move an issue to this column the resolution is set to "done" and the issue disappears (in the running sprint). After closing the sprint it is not shown as completed in the sprint report.
I am not sure what to do, as some answers say "the resultion must be set to done", but if I do that it disappears from the sprint and from the board without beeing in the report. On the other hand, if the resolution is not set it stays unresolved but disappears from the board after closing the sprint anyway (even if the status should be shown regarding to the filter adjustments).
Is there any "best practise" for
I have a simple target
Closed issues should be visible in the report but should disappear from the board and should be resolved after closing the sprint. Is that possible? Otherwise I have no idea how to work with team velocity and ressource planning.
Regards
Michael
Welcome to the Atlassian Community!
The resolution is probably irrelevant to this problem.
You need to look at why the "issue disappears from the board when it is moved to the 'ticket closed' status".
You have the status in the right-most column, which is what determines "done" in a sprint (and hence the sprint report), so it's not that. But if the issue disappears from the column when moved into it, it's effectively being removed from the displays of the sprint.
My guess is that your board filter is broken - it's not selecting for issues that are done, so they vanish. Given what you are seeing, I suspect you have one of these two problems:
Note that the first one works by excluding issues in your last column, and the second will exclude resolved issues.
To fix the problem, we need to find out why your issues vanish from "done"
Thanks for your quick response!
I think it's quite simple. The filter says "resolution is empty". But what if I delete this in the filter? Would the board show all resolved issues from the past ongoing? The issue navigator does exactly that. Several 1.000 issues as the filter result.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, the board only displays issues in the current sprint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To avoid misunderstanding., thousands of issues have been closed in the past without beeing in a sprint before (the company was not really familiar with jira). That leads to thousand of issues in the backlog, doesn't it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No. The backlog is a different list. You can think of it as adding three things together:
As long as your old issues are in one of the status in the last column on the board, they won't show in the backlog, even if they have not been through a sprint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again,
I removed "resolution is empty" from the filter and currently one issue is with "closed" status in the right column. Looks like you solved it as no other closed issue is visible in the backlog or other planned sprints!
Many many thanks!!!
Regards
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.