Swimlanes are not working and tickets on boards are missing

[Kevin Cornuot]

Hello everyone,

I'm trying to put some swimlanes in my board but I'm having troubles making everything work : 

- First, what's the difference between "regroup by" 

and swimlanes ? 

I'm guessing one is linked to the user display and the other one is the "default" one for the board ?

- Second, the boards are missing stories BUT are here when running the filter : I'm missing the COM-290

 

Here the filter is giving back my 9 tickets, with 5 stories absolutely similar, but in the board with the exact same filter, only 8 are showing : 

I even have another board with swimlanes straight up not working :

Filter : 

config : 

and guess what ? no swimlanes but my two tickets are in the board, here is one

(I know I have a filter on but even OFF it's not working. I'm displaying the due date in the card to be sure)

Can someone help me ?

[Marc - Devoteam]

Hi @Kevin Cornuot 

If you are not using swim lanes, the group by option groups issues of the same type or by the same project. This is not board configuration

Swim lanes are based upon assignee of issues, based on an issue type and in the columns the child issues of the swim lane issue will be shown.

I can't see why it fails.

On the 2nd board a quick filter RDR is active, this is might the issue.

Otherwise the issue is the main board filter, does this include issues from project BNB?

[Kevin Cornuot]

As I said, the filter isn't the issue (i'm taking a screen with just the top of the board to show there is no swimlane as I have no time to hide the infos that I want. But we can see the top of the tickets instead of the swimlane NOW)

[Marc - Devoteam]

Hi @Kevin Cornuot 

I think you misunderstand the concept of a board.

Anything that will be shown in a board is based upon a filter, if an issue is not in the filer its not on the board.

Columns on the board contain statuses from the workflows used in issues that are on the board.

So if you have an issue with status "to be worked on", creating a column on the board with title "to be worked on" will no say the issue is on the board.

The issuer needs to be in the filter, if its not it will never be on the board.

Swim lanes are used to visualize issues on the board, based on the said filter. Setting swim lanes based on a filter, means is a sub filter, based from the main board filter.

[Kevin Cornuot]

Hi again @Marc - Devoteam 

I think you're not reading my messages.

- First, I told in the initial post that I knew I had a filter on but taking it off didn't change anything, yet you still asked ?

- Second, I know how filters and boards works, that's why I'm having an issue here, because it's not working as it should be. That's why I linked the result of the filter used in the first case

- Third, I answered to you telling you that I made a screen but didn't want to show the tickets as I had no time to hide the infos. I now took that time and took another screen showing that the two tickets are not in the swimlane despite being in the board :

- The two tickets are brought by the board's filter request

- No board filter is active

- The two tickets are eligible to the swimlane as shown in the results of the filter swimlane query

- The two tickets are not creating the "NOW" swimlane

[Marc - Devoteam]

Hi @Kevin Cornuot 

I see the issue now.

Atlassian probably did something now.

The group by seems to have replaced the swim lane feature. The swim lane feature doesn't respond to anything anymore on the group by works.

I suggest to raise this as a BUG and let Atlassian explain this

I would like to hear the answer.