You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I work on a project (Project 1) with some dependencies with another project (project 2).
To make it easier to manage I have created a cross-project release and a plan that includes both projects filtering the relevant tasks for Project 1 from Project 2.
The problem is that in the plan I don't see how to group the tickets in the same release. Although I have a cross project release in the plan I see the two individual releases for each project, making it kind of useless, duplicating initiatives and making it very hard to see the dependencies.
In the example I have:
I want to have both epics under the same release and be able to see the dependency. Having cross-project releases and then seeing them in separate releases is not very useful.
Thank you for reaching out.
Although the way cross-project releases are displayed on the Advanced roadmap view is designed as intended, we understand that it might not fit some scenarios.
Unfortunately, that view can not be changed today, so we created the following feature request to consider the implementation of a different layout for Advanced roadmaps, where a cross-project release can be grouped into a single swimlane instead of two:
Feel free to vote and watch this suggestion to increase its priority and receive notifications about any updates.
Let us know if you have any questions.