Is it possible to show a ticket in more than one component on a single sprint board?

[Deleted user]

Hello,

as allready mentioned in my headline i have the following question:

"Is it possible to show a ticket in more than one component on a single sprint board?"

Issue right now:

If i create a task with more than one component and drag and drop this task into my sprint planning i only see the ticket in one of the components (by the way: swimmlanes = components in my board).

For example:

Ticket1 belongs to component A and component B. In the sprint board it is only mentioned in the component A. 

side facts:

- Our project is structured by components

- We are using a Scrum Board with components as swimmlanes

kind regards,

Niklas

[Bill Sheboy]

Hi @[deleted]  , and welcome to the community!

What are you using components to represent?  For example, when components are related to solution pieces, the simplest approach may be to have separate work items rather than have a single Jira issue represent two pieces of work.

Best regards,

Bill

[John Funk]

Hi @[deleted] - Welcome to the Atlassian Community!

So, do you really want to show an issue linked to multiple components (that is easy enough) or do you want to show the issue in multiple Swimlanes? This is not possible in Jira. An issue can only appear in one Swimlane. 

[Deleted user]

Yes i wanted to show them in multiple Swimlanes...

[John Funk]

As I said above, that is not possible in Jira. Another option which Ignacio suggested is to use Quick Filters with a single Swimlane. 

Finally, you could actually create a different board for each Component with the sub-filter based on the component. 

Not much else you can do

[Deleted user]

Hi Ignacio,

thanks for that fast answer. Unfortunately the project has over 10 components, which would cause a lot of swimmlanes….

So there is no other solution?

[Ignacio Pulgar]

For this use case, maybe it's better setting 10 Quick Filters (1 per component) instead of 10 swimlanes.

It may also be helpful including the Component field in the card layout. That way you will easily detect issues belonging to several components with no need for selecting them.

[Ignacio Pulgar]

https://confluence.atlassian.com/jirasoftwarecloud/customizing-cards-764478020.html#Customizingcards-fieldsAddingfieldstocards

[Deleted user]

Quick Filters are allready in use. But they dont look as good as sorted by swimmlanes...

Nevermind thanks anyways.

[Ignacio Pulgar]

Hi Niklas,

The board swimlanes have been designed to work this way:

For each issue returned by the board's filter, the top-most JQL query in your swimlanes definition will be executed. If the issue would be returned by that JQL, then that issue will be assigned to that swimlane and the next issue will be processed.

Otherwise, the issue would be tried to match the next swimlane JQL, until it matches one. If the issue matches no swimlanes, then it will be added to the very bottom of the board, under Other Issues swimlane, and process will continue with the next issue.

That said, there's no way to make the same issue appear twice in the same board.

Maybe, creating an additional swimlane on top position (above all existing ones) might be considered with the following JQL:

component = <component A> AND component = <component B>

So issues matching those two components at once would be assigned to this new swimlane.

Hope it helps.