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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi, I'm concerned about potentially impacting an existing Parent Link (Epic Link in this case) of an issue without realizing it due to Review Changes screen not reporting a pending change.
The scenario - I have an issue that was created in Project A that is a child of an Epic in Project B. I don't currently have Project B in my Advanced Roadmaps Plan scope, so I'm not seeing the relationship that exists - and I had no idea Project B even existed (my org has many many projects). One day, I inadvertently change the parent Epic of my issue to one that is in Project A because I don't see any relationship to Project B in my plan and when I do Review Changes, the "Current" state is reported as empty ("-") so I assume it is safe to apply the change.
Is there a way to ensure I will be warned about overwriting a potentially important associations with external projects - without being required to have full visibility into external projects that I may or may not be aware of?