How to put a single ticket on two different Active Sprint Boards?

[Christoph Lühr]

My team is the owner of an artifact other teams also contribute to. Therefore we have to do code reviews for every contribution they make. To make the efforts visible on our sprint board we would like to show their tickets on our sprint board.

I already adapted our board filter for this and the tickets are showing up on our board. But: it seems I cannot control in which of our sprint boards the ticket appears.

Team A and Team B work independent from eachother. Team A creates tickets, assigns them to their sprint and starts the sprint. The tickets show up on their active sprint board. Team B have an active sprint themselves. The mapping of the board columns is done and their board filter is properly adapted so that it shows the tickets of Team A, that have a certain label set on their board, too. Weird thing is, that the tickets with the corresponding label, which are in the active sprint of team A are automatically shown in the currently active sprint of team B. It seems team B cannot schedule the tickets for a specific sprint, they are just in the currently active sprint.

[Cristian Rosas [Tecnofor] · Accepted solution]

Check this:

https://confluence.atlassian.com/jirasoftwarecloud/planning-sprints-764478112.html

And issue cannot be in 2 active sprints at the same time. You need to split the issue into 2 and link them to do the thing you have asked for.

[Christoph Lühr]

OK, this is what I assumed. Thanks for the answer. This is actually what we did before. We thought, that there might be a way to avoid the additional overhead of creating and maintaining two tickets for basically the same task.

[Cristian Rosas [Tecnofor]]

Mmm well, with some automatisms you could create a clone of a ticket with an issue linking between them...

It could be done in a listener or in a transition... that could be an interesting option.

[Alexey Matveev]

Hello,

Have a look at the board filters for Board Team A and Board Team B (board settings -> General) and make sure that the filter from Board Team B does not select issues from Team A.

[Christoph Lühr]

The problem is not that tickets from team A are generally showing up on the board of team B. The point is, that team B needs to be able assign the tickets of team a to a sprint they want, without changing the assignment of team B's sprint. The specific tickets of team A need to be in a sprint of team A and in another sprint of team B. Both teams need to be able to control in which of their sprints the shared tickets are.

[Alexey Matveev]

Do you mean that you want the same ticket to be assigned to two different people in each board? If so, then it is not possible.

Tickets look the same on all boards.

[Christoph Lühr]

No, it does not have to be assigned to different people. We just want to make transparent, that someone of team B has something to do with the ticket of team A. Our Jira board is our source of truth. What's not on the board, doesn't basically exist for us.

It just has to be in two different sprints, thus on two different boards and we need control about in which two different sprints it is.