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; } } }

Swimlanes based on JQL for labels are not showing

Lianne_Harrison

I have completed scoured the internet to resolve this issue but haven't been successful.

I have a board that uses swimlanes to categorise work based on a label. The JQL for this is the same as every other swimlane however, one in particular does not show any Jira tickets at all.

I have double checked the filter to see if it was accidentally filtering out that type of project but the filter works just fine and I can see those tickets in that list, so I am baffled as to why they will not appear in that particular swimlane.

They do however, end up in a different swimlane and I wonder if there is a hierarchy that the JQL uses. For example, will a swimlane filtering just by a project override another swimlane filtering just by label? In other words is it a bit like CSS specificity whereby the more specific the JQL query, the more likely it is that the swimlane will pull through that ticket?

I hope this makes sense

Accepted answers

John Funk

Hi Lianne - Welcome to the Atlassian Community!

There is a hierarchy to Swimlanes starting with the top most Swimlane. If the ticket matches the criteria for the top Swimlane, then it will land there. If not, then the next Swimlane. If not, it continues to the bottom Swimlane, which should always be something like Everything Else.

You can change the order of the Swimlanes by going into Board Settings, then Swimlanes, then simply drag the Swimlane up or down.

I hope that helps!

Krister Broman _Advania_

If you do not use the swimlanes do the tickets show up?

If they do not, have you looked at your board filters in the "General and filter" section to see if you are filtering out those specific issues.

That said, you will only find one issue at one place in the board, so if you have

priority = major in lane 1
issuetype = task in lane 2

then you will get any major case in lane 1 irrespective of there priority.

In lane 2 you will get any task.

Any task that is major will however be in lane 1 as they have already been added to the board.

All comments

John Funk

Hi Lianne - Welcome to the Atlassian Community!

You can change the order of the Swimlanes by going into Board Settings, then Swimlanes, then simply drag the Swimlane up or down.

I hope that helps!

Krister Broman _Advania_

If you do not use the swimlanes do the tickets show up?

If they do not, have you looked at your board filters in the "General and filter" section to see if you are filtering out those specific issues.

That said, you will only find one issue at one place in the board, so if you have

priority = major in lane 1
issuetype = task in lane 2

then you will get any major case in lane 1 irrespective of there priority.

In lane 2 you will get any task.

Any task that is major will however be in lane 1 as they have already been added to the board.

Lianne_Harrison

Hi John

Thanks for the welcome!

So I just tried dragging that swimlane to the top to see if that made a difference but sadly, it didn't.

It must be something else I am doing wrong, although that is useful to know!

Lianne_Harrison

Hi Krister

Yes, if I do not use swimlanes, the issues do show up which is a good start.

I have a swimlane just for that project type, based on JQL query. I then have another swimlane that should filter for the project type AND a specific label. It's the latter one that isn't working as the issues show up in the first swimlane that just filters for that project.

For example

Swimlane 1 - project = BAU

Swimlane 2 - project = BAU AND labels = upgrades

It's the second swimlane that isn't pulling any issues through

Krister Broman _Advania_

You have to switch the order so that the specific lane comes before the general lane

Lane 1: project = BAU AND labels = upgrades

Lane 2: project = BAU (= any remaining BAU issue)

An issue will only appear once, so when assigned it will not reappear even if it matches the JQL once more.

Lianne_Harrison

For some reason, this morning, the ordering of the swimlanes has made the filter work!! So thank you to you John and Krister below as you were both right!!

Thank you very much for your help

Lianne_Harrison

As mentioned above, the swimlane ordering this morning did make a difference, so thank you for your help with this!

Dimitris Haristos

Hi @Lianne_Harrison

I have the same requirement, though it seems that an Issue is shown on other swimlane because it can appear only once on board.

So, as mentioned most probably there is a hierarchy in JQL indeed.

Have you tried to re-order the swimlanes, just in case?

Cheers,
D.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server