Kanban Board Queries Using Assignee and Additional Assignee

[Matthew Couture]

I have a team that uses both the Assignee and Additional Assignees field to assign multiple users to tickets. They have requested I come up with a view on their Kanban board that shows all tickets assigned to each team member, using either of these fields.

I attempted to do this by setting up swimlane queries for each user in the board settings:

assignee = <team member> OR "Additional Assignees[User Picker (multiple users)]" in <team member>

However, it appears the Kanban board will only show each ticket once, so tickets assigned to multiple users are only appearing once, and which user-specific swimlane they appear in appears to be random.

Does anyone know a way around this, or have any suggestions for another view I could create that would solve this problem?

Thanks in advance!

[Gor Greyan]

Hi @Matthew Couture

Welcome to the Atlassian Community!

You’re right — Jira’s Kanban board architecture only allows a single visual instance of each issue. Even though an issue might satisfy multiple swimlane queries (e.g., both assignee = userA and "Additional Assignees" contains userB), Jira won’t duplicate that card. It picks one swimlane “match” — effectively at random — to display the issue in. Unfortunately, there’s no native workaround that allows the same issue to appear multiple times within one board view.

Alternatively, you can create a Jira Dashboard with a gadget per team member, using a filter like:

assignee = <user> OR "Additional Assignees[User Picker (multiple users)]" in (<user>)

[Ignacio Vera]

Here are a few workarounds that might help:

1) Dashboard view
Create one Filter Results gadget per user with this JQL:

assignee = "User A" OR "Additional Assignees[User Picker (multiple users)]" in ("User A")
That way you’ll see all tickets for each person — without the board limitation.

2) Quick Filters (if you only have a few users, best option in your case)
Instead of per-user swimlanes, create quick filters for each team member using the same JQL.
It won’t duplicate issues either, but it’s a quick and effective way to focus on individual workloads.