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.
I am new to using advanced roadmaps and have a question about how to properly rearrange project timelines and version them correctly using the scenarios feature. For example I have a set of stories for a given project and business would like me to provide two separate timelines. In timeline A I wish to have some group of stories or function go first and take priority over group B, they need be completely separated in terms of which sprints they are worked just that one is weighed heavier than the other. In the second scenario I wish to find out the opposite (B before A). Business would like to have two separate versions of the timeline so that they can see when things would be completed. The issue lies with the fact that the scenarios are tied to the underlying Jira stories so if I update a field lets say target start date and I save my changes in one version of the scenario it updates the others. I had initially thought of just not saving my changes but in that scenario I am the only one that can see the two versions of the timelines which isn't super useful. I'm wondering if there is a better way to do this so that the versions truly are independent and modifying the ordering of one version does not impact the others.
Saving changes to your plan and committing changes to Jira are two different things in Advanced Roadmaps.
As you make changes in your plan, your plan is saved automatically, you don't need to do this manually.
Once you're happy with your plan, you can commit the changes to Jira.
In your case, if you hold off on committing any changes to Jira, you can build and share two scenarios without any negative consequences.
Best of luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.