We use a rapid borad to plan and visualize the content for certain teams in the long run. From period to period there is new planning and we would like to show which of issue we take on in the new period (i do not want to call them sprints, because they are not).
Unfortunately the top most swimlane catches an issue and the issue is not *catchable* anymore by swimlames below the first one.
Is there a way to achieve that behaviour and show an issue on multiple swimlane?
I don't think it is possible to show one issue several times in the same board. The swimlanes is just a way to sort and group the content on the board.
There is one situation though when an issue can show twice and that is if you have an issue with a sub-task, then the parent issue will be shown (greyed-out) above the subtask if the parent and subtask are in different columns, but that is a completely different thing.
If you need the issue to show in a swimlane below you will have to work on your swimlane queries more.
Thanks for the explenation. It seems obvious now that this is not possible :S Since the swimlanes are a way of filtering and grouping of the underlying board filter.
We might reconsider how we structure our issues. Maybe we should use parent - subtask relationship for that as you suggested.
It should be allowed. For example, I have created custom fields like Developer Assignee, QA Assignee and I have configured my board JQL on Developer Assignee for Developers and QA Assignee for QA Engineers. Now I want to see the task at both Developer's swimlane as well as QA's swimlane. This will give me a better view of all the running tasks, when I am seeing with respect to a Developer's tasks or a QA Engineer's tasks.
I was facing the same problem. When two people collaborate on a single Jira ticket, we use a custom field to mark the second assignee. I wanted that one ticket to appear twice - in two swim lanes, each swim lane belonging to one team member, one as an assignee and one as a second assignee. But I couldn't do it, for the reasons outlined in this chat above.
The workaround I found was to combine Swimlanes with Quick Filters. I configured Swimlanes with the Assignee field and Quick filters with the custom field (e.g. Second Assignee in my case). When I then select one value in the Quick filter (i.e. a person who is a Second Assignee) the swim lanes will display such tickets even though the main assignee is somebody else.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events