Do Kanban Swimlane JQL queries have to be mutually exclusive?

[Amy_Hall]

I have configured swimlanes on my Kanban board for each component as describe in the documentation here.

https://confluence.atlassian.com/jirasoftwareserver073/configuring-swimlanes-861254428.html

However, because components is a multi-select field, project members can enter an issue that has multiple components associated with it.  In this scenario, the issue only appears in the first swimlane where it matches the component.  This is confusing to my users.  

Can you configure a board to allow an issue to fall into all swimlanes if it meets the criteria of that swimlane or are we stuck with this behavior?

[LeKisha Boswell · Accepted solution]

Issues are usually assigned to one swimlane by default as the swimlane helps to group items in order to organize tasks and prevent confusion. Considering swimlanes are used to group common issues you might want to consider using stories or sub-tasks to further break down your tasks so you can group them accordingly. Using a parent child relationship when creating issues may provide some resolution. 

[Nic Brough -Adaptavist-]

Ideally you should make them exclusive, to avoid the problem.

The problem you describe with it confusing your users is actually worse if you allow a card to be seen twice - people start marking things as duplicates and complaining that changes to one affects the other.  I'm afraid you can't change over to show multiple cards.