Items are showing in everything else group

[Johnson_ Jeff _RIS-OKC_]

We are seeing items dropping into a group of "Everything Else".

I thought this was related to newly created items on the board, but noticed others which were not new. 

 According to Atlassian searches, this is related to the board filter or Quick filter in effect.

 However, I cannot find anything in the filters which is causing this to occur other than the items are newly added to the sprint or Kanban board after the migration.  I was hoping this would correct itself overnight and it did not.

 Steps Investigated:

1. Reviewed board filters.  As seen below, they are basic filters only.
2. Reviewed a couple of the Quick Filters.  Fixed Quick Filters where they were showing an error due to Cloud version of JQL. 

The filter for the boards is very basic and the swimlane is set to Stories

project = ProjectName AND "Team(s) Assigned" = Team Name ORDER BY Rank ASC

[garrett_lessard · Accepted solution]

Hi @Johnson_ Jeff _RIS-OKC_ 

Look closely at an "Everything else" issue

Pick one issue from that section and check its details:

• What issue type is it?
• If it is a Task or Bug, does it actually have a parent Story assigned?
• If it is a Story, remember that when swimlanes are set to Stories, the Stories themselves become the headers. Only their sub-tasks or child tasks show up inside the lane. Stories without child items, or Stories that are pulling onto the board as cards, will end up in "Everything else".

Check if your board filter is hiding parent Stories

Your current filter is: project = ProjectName AND "Team(s) Assigned" = Team Name ORDER BY Rank ASC

This causes problems if a Task has the Team field filled out, but its parent Story does not. Jira cannot build a swimlane for a Story that is filtered off the board, so the child Task gets dumped into "Everything else".

To test this, open an issue from the bottom bucket and find its parent Story. Check if that parent Story has the correct Team assigned. If it does not, you need to update the Story or change your filter so it includes these parents.

Watch out for migration bugs

If you recently moved to Jira Cloud, the way Jira handles hierarchies might have changed. The old "Epic Link" is now just "Parent". If your issues lost their links during the move, Jira cannot group them by Story anymore. Check a few issues to see if their parent connections are totally blank. If they are, you will need to bulk-edit them to restore the links.

Next steps to fix it

• If you want Stories as headers: Make sure every Task or Bug has a parent Story, and make sure those parent Stories match your board filter.
• If you just want to group cards by worker or project: Change your swimlane settings from Stories to Assignee or Epics instead.

Cheers, 

Garrett Lessard Appfire Expert Services

[Johnson_ Jeff _RIS-OKC_]

Subtasks appear to be the issue.

On-Prem to Cloud migration last weekend.

Thanks for the heads up!

I passed this along to our LNR support community.

[Shalini Pradhan]

Hello @Johnson_ Jeff _RIS-OKC_ ,

Good day! Welcome to Atlassian Community :)

When swimlanes are set to Stories, the board creates one swimlane per parent Story that has subtasks. Any issue that does not fit as a subtask of a Story or any story/workitem which doesnt have any subtask,  are not shown on the board and falls into "Everything Else." 

• Validate your board once and the workitems under Everything else, if they have any subtask or not

[Johnson_ Jeff _RIS-OKC_]

There are two subtasks under the story item in question on the board.

[Fabio Racobaldo _Catworkx_]

Hi @Johnson_ Jeff _RIS-OKC_ and welcome,

do you have some swimlane configured in your board?

Let us know,

Fabio

[Johnson_ Jeff _RIS-OKC_]

the swimlane is set to Stories