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
Next: Root
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.
I have created our first plan. As it was our first exercise it has about 700 uncommitted changes. As I plan out next month am I better off-
a) creating a new plan and include some of the existing epics that overlap and add new ones or
b) just keep adding to the existing plan
I see the new plan option as cleaner but wondering about the downside
I agree with Cameron. Enabling scenarios will give you another playground to work with without impacting the "original" changes. You can choose to Commit from either Scenario as well.
I would also suggest that you commit the original changes. The phrase I tell folks is, "Commit early; commit often." That way you don't have to review all of them, just the most recent few.
I consider most changes "safe" when creating a new Plan because you're likely doing the following things:
About halfway down the page on the link below, it will tell you what you're likely committing down to Jira. Of course, you can always select just a few at a time instead of committing all 700+. :)
Cloud - https://confluence.atlassian.com/jiraportfoliocloud/committing-your-plan-changes-828785217.html
Server - https://confluence.atlassian.com/jiraportfolioserver/committing-plan-changes-802170515.html