Hi - I cannot see resolved and closed issues in the scrum board even though the Board filter shows the issues.
Can someone help? Sub-tasks are visible but no issues are visible even in the backlog if they have been closed or resolved
Hi Arun
Did you check the board settings? I believe that you may not have those status properly mapped in the scrum board.
So, please review the configuration using the following link as your guideline:
https://confluence.atlassian.com/display/GH/Configuring+Columns
Also, perhaps you should raise a new support ticket for an advanced assistance.
Cheers,
Paulo Renato
The status are mapped correctly in the configure section of the board. Specifically - Resolved and Closed statuses are mapped to the Done column.
But they still dont show up in the planning board. What else can I do?
Can someone reply please?
It is by design. Resolved issues are not shown in Planning. Can you tell me why do you need to have resolved issue in planning, isn't it contradicting the whole concept of resolution?
EDIT: I stand corrected, the resolution really does not matter. It is purely based on the status that is mapped to the last column of the board configuration.
So if the 'Resolution' status is mapped to the last column (the traditional JIRA workflow), it will not appear in the planning board as the issue is considered none.
It is not showing up on the work board, I do understand the reasoning behind planning. But if I start a sprint with certain resolved issues, they should show up as done so I can have a good view of whats done and whats in progress.
Hi, I am having the same problem. We have recently migrated a project from mingle to JIRA, and would like to track previous iterations (sprints) using the agile board. Would this be possible to accomplish?
The board settings are correct. I'm having the same issue.
Same issue here.
We use our own custom workflow and have every states/stages/steps in de workflow mapped to one of for columns on the scrum board (To Do, Doing, Verify and Done).
The filter on which the board is based shows the Closed issues as well, but they don't appear on the board in the Done column.
Any help would be welcome.
We use JIRA 7.2.4.
The boards have changed significantly in the last 5 years, but we can still try.
What exactly does the board filter say, and are your "closed" issues showing as being in the current sprint?
In our scrum projects, issue is resolved when bug fix is done, the resolved issue is closed when QA verifies it as working as expected. In that case displaying resolved issue does makes sense, also the current sprint if issue is Closed, scrum master might want to know the reason (in case if he/she wants to see the status), there could be 15 issues in a sprint and relatively hard to remember.
In any case hoping to see a workable action from Atlassian.
In the real world, there will always be work items you want to track in a sprint, even if the work was finished by the developer early, like the day before you developed the sprint board. Our QA still needs to be able to view what to test at the end of the sprint. To not be able to put resolved items into the sprint for tracking is a significant deficiency.
An item should only be resolved when it is done. Otherwise you are lying to your people. If it is done, it should be at the end of the current sprint and because it's done, it won't go into another one.
In the case you mention, the issue should have been added to the sprint in which the developer finished it when they picked it out of the backlog as an "item beyond commitment because we have capacity"
For my teams it's useful to meet with the PO and talk about sprint priorities in the same backlog view with stories marked as complete. Usually this wouldn't be a problem in our normal workflow but we have run a Kanban style board and are switching over to Scrum mid "sprint" so we have more flexibility (running a Kanban board with a backlog view). So all of the work we have completed is lost unless I re-open stories.
Is there another way to trick jira?
No, you'd have to change your process such that you stop thinking done things are done and have no idea of what needs doing.
If I were you, I would stop the already broken process of switching between Scrum and Kanban. Decide on a single way to work and stick with it.
It looks like you're new here. Sign in or register to get started.
