Done bug showing up in the backlog

Jennifer Baum February 17, 2023

I have a bug that is marked 'Done' and is showing up in my Kanban backlog.  I also noticed that there are 2 'Done' fields (see screenshot). 

I haven't seen this before and this seems to be the only bug I've found with this behavior in this project and plan.

Where does the 2nd 'Done' status come from? Why does this bug have 2 fields for status and others sharing the same plan do not?  Why is it showing up in the backlog if it is done?  How can I get this removed from the backlog?

Thanks for any help you can offer.

Jenn.

donebugbacklog.jpg

2 answers

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 17, 2023

The backlog does not list issues that its parent board considers "done", but it is not looking at the status (directly), status category or resolution.

On a board, an issue is "done" only when it is in the last (rightmost) column on the board.  

So, check the board configuration - is your "done" status in the last column?

Jennifer Baum February 23, 2023

Yes, done and cancelled status' are in the far right done columns.

Monica Brazelton
Contributor
June 7, 2023

@Nic Brough -Adaptavist- Coming back to this since it seems similar to a question I just shared! In my project, the "Done" status is mapped to the far-right column on the sprint board, and all the "Done" tickets still appearing in the Backlog have their Resolution field set. 

The sprint they're in is still active but overdue - would this possibly cause the "Done" issues to appear in the Backlog, or is there something else I'm not thinking of? Or is this a bug?

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 7, 2023

@Monica Brazelton 

Since your question is about a Scrum board and this question is about a Kanban board, the scenarios are not the same.

I've added a response to your original post.

1 vote
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 17, 2023

Hello @Jennifer Baum 

First, I'll address the "two Done fields". These are two separate fields.

  • The "Done" shown in the green box with the pull-down arrow is the Status field for the issue. 
  • The "Done" value to the right is the Resolution field. When an issue is changed to a "done" Status the Resolution field is used to give additional context to the nature of the work completion; i.e. Done because we Cancelled it, Done because we're Done with the changes, Done because we Won't Fix it. The Resolution field should have a value only when an issue is in a "done" (green) status. When it is in any other status the Resolution field should be empty. The Resolution field is used by Jira native reports such a Created vs. Resolved to determine if an issue has been Resolved.

As to why the Done issue is showing up in your Kanban backlog, I need more information.

The Backlog screen lists the issues in two groups with one group displayed above the other. The lower list always has the heading "Backlog". The heading for the upper list can vary. Example:

Screen Shot 2023-02-17 at 2.04.49 PM.png

 

Is the "Done" issue appearing in the lower list or the upper list?

Is this board for issues in a Company Managed project or a Team Managed project?

Jennifer Baum February 23, 2023

So the 2nd done drop down must be a new field or one I haven't noticed before. Thank you.

My board has 3 columns with aligning status': To Do is status = Selected for Development, In Progress is status = In Progress and Done with status = Done, Cancelled.  Backlog is aligned with status = Backlog.

Maybe there was a delay in the update to the board but I can no longer find the issue in the backlog. It seems to have resolved itself.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events