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
Realistically the only way to do this at the moment is to take snapshots of the plan using the Export CSV feature (see https://confluence.atlassian.com/advancedroadmapscloud/sharing-and-exporting-plan-data-998651329.html )
At some point in the future we would also like to provide the ability to export the plan as an image (which you could use to visually compare) but unfortunately I can't commit to when we will be able to deliver that feature,
Hi @Ollie Reid,
Can you provide a bit more context on how it broke then dates.... in theory there are a couple of levels of protection for this. Firstly you have to actively accept the auto-scheduling suggestion and then you need to save the changes from your scenario back to the rest of Jira.
So in theory you could have either cancelled the auto-scheduling or discarded the changes? I'm guessing that in this instance you didn't notice until it was too late and you now want to compare with a previous version of the plan and restore the previous date values?
The changes made should be in the change history of each issue, but depending on the size of your plan that could be an arduous task to recover those dates.
So in this case is the goal not just to be able to compare with a previous version of the plan but actually to be able to import or restore the data?