Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you will find the site temporarily inaccessible. Thanks for your patience. Read more.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Kanban Boards: Swimlanes based on 1st (first) component (display tickets only once)

Gerhard Koiner November 20, 2024

Hi

I created a Kanban board with query-based swimlanes (component = ...). The problem is, when I have more than 1 components the ticket will show X times (X = number of components in ticket). I would only like to see the ticket once (first component). Any ideas (within "standard", without my admin? Thank you

2 answers

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 20, 2024

Hello @Gerhard Koiner 

Welcome to the Atlassian Community.

First, a given issue will display in only one swimlane. It cannot display in multiple swimlanes. If you think you are experiencing that, please provide a screen image.

When creating Swimlanes based on Queries, each issue will appear in the first swimlane for which it matches the query.

In my board I created two swimlanes using queries that each select a single component.

Screenshot 2024-11-20 at 8.39.26 AM.png

 

In one issue I set the Components to only "Ack-component-1". In another issue I set the Components to only "Ack-component-2". In a third issue I set the Components to include both values. I added the Components field to the card display so that you can see how they end up in Swimlanes.

Screenshot 2024-11-20 at 8.39.13 AM.png

The issue that has both values is displayed in only one swimlane; the first swimlane where the issue matches the JQL.

I'm not aware of any method to determine which Component value in the field is "first". I think when viewing the values in the field they are sorted alphabetically, so you can't tell which one was added first vs. later. But if an alphabetic sort is what you mean by "first" then you would just arrange your swimlane queries in that order.

Gerhard Koiner November 20, 2024

Hi Trudy, thanks for replying in depth. As a matter of fact, I see the issues twice or even more often, depending on the number of components that are assigned to the issue. But, we are using an on-premise instance of Jira, maybe there is a different behaviour in this setup?

I will attach a screenshot tomorrow.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 20, 2024

I assumed you were using the Cloud product because of the tags on your post.

Screenshot 2024-11-20 at 11.07.48 AM.png

Deployement Type = Cloud indicates you selected a Cloud (SaaS) product. 

Product Plan = Standard indicates that the Cloud product you selected is running under a Standard subscription plan.

The first thing presented when using the Ask the community feature is a list of your products from which you can select. If you are using an on-premise (Server or Data Center) instance then perhaps you chose the wrong product when opening your Question.

 

I will check the Swimlanes by Query configuration in an on-premise instance and post about my findings.

Like Gosia Adamska likes this
0 votes
Gosia Adamska
Contributor
November 20, 2024

Hi Gerhard,

I think it's not posible to have one query for many swimlanes. I think you should create a separate JQL query and use them for each swimlane. Meaning 
component = "alpha" for one swimlane and component = "beta" for another swimlane.

Let me know if you've found some other workaround.

 

Gerhard Koiner November 20, 2024

Hi Gosia, what you are describing is exactly what I have done. It would be nice if the „standard swimlane options“ would include more options ;-)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events