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'm using a portfolio plan across multiple projects (for simplicity say project A and B) with a 5-level hierarchy connected via parent links.
What is frequently happening is that I accidentally create child issues in the wrong project and I'm looking for a way to limit parent links to not work across projects, so issues in project A can only have parents in project A and vice versa.
My issue specifically is that say I have an issue in project A and click the + button to add a child issue, this child issue by default will sometimes be created in project B instead because I think portfolio plans use the last project I created an issue in instead of the project of the immediate parent I am trying to create an issue under.
I'm still using the legacy portfolio live plans if this makes a difference (since the new interface is still unusable) but even without plans it would be great to only see available parant issues from the same project when editing an issue for example.
This is basically the same issue as exist with epics in standard jira (https://jira.atlassian.com/browse/JSWSERVER-12016) with all the same arguments.