nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

A few swimlanes for a board

Piotr Rogoża

Hello

I have a few swimlanes for a project. But there is also an issue with them.

For example, I have 10 isssues for project. Swimlanes are configured to use queries.

1st query matches to 7 results. 2nd query matches to 5 but only 3 are displayed. Next queries aren't displayed.

Is it possible to display all queries, even duplicated?

I'm using Jira Server 8.4.

Best regards Piotr

Accepted answers

Nic Brough -Adaptavist-

You have almost answered your own question:

> I have 10 isssues for project. [...] 1st query matches to 7 results. 2nd query matches to 5 but only 3 are displayed. No more displayed

This is correct - 7+5 is not 10.

Jira makes the assumption that the swimlane at the top is the most important to you, and then each one below it is in decreasing order of importance. If an issue matches the first swimlane query, it will land in there, and not be displayed in others.

You should never have a card on the board more than once, as that is confusing and wrong.

All comments

Nic Brough -Adaptavist-

You have almost answered your own question:

> I have 10 isssues for project. [...] 1st query matches to 7 results. 2nd query matches to 5 but only 3 are displayed. No more displayed

This is correct - 7+5 is not 10.

You should never have a card on the board more than once, as that is confusing and wrong.

Piotr Rogoża

Thanks for answer.

Is it to possible change this behavior? But not for all, for whole instance of Jira, but only for specific boards.

Nic Brough -Adaptavist-

No, the boards display issues once. It would be a nightmare to have them duplicate cards.

Andrej Marsic

@Nic Brough -Adaptavist- nightmare why and for whom?

We would need this feature, as we'd like to have a view on the board that quickly shows how many issues and at what status they are in the board based on the different queries... but the assumption that is made prevents this. I'd rather have a nightmare than a lacking feature.