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 have cross-cutting Portfolio Epics that are being worked by different Teams. Each team has its own Plans View, however, when removing an Epic that does not correspond to Team A from the Advanced Roadmaps Plans View A, it also removes it from the Team B Plans View. How can I prevent this from happening? I would like for the Epic removed from the Plans A Team to remain in the Plans B view/team.
Welcome to the community. Please clarify what do you mean by views? Does Team A and Team B have their own plan? Does your teams all working against one plan but using different views hosted under the same plan?
If so, then when object (i.e. Epic) is removed from the plan, then it will drop-off from all of the views within the same plan.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
By view I meant that we have "Saved As" different views for each different product team. I don't believe we have created different "plans", per team.
It sounds like we would need to create different "plans" in order to avoid this?
I can check with our admin to see how to go about that.
When you dealing with views within the same plan, the source content behind each view is the the same. When you remove an object (Epic) and saved the changes back in Jira in View A, then you are essentially removing it from the source content. Therefore, View B is impacted.
Yes, you will need to have different plans. Keep in mind, if the two plans are also sharing the same content (same Jira project etc..). Be careful on what your issue sources that your plans are pulling in, since one still can save changes back to Jira projects and thus impacting the different plans can still happened.