Does it influence the sprints after confirm to save changes to JIRA in advanced Roadmaps

[Renato Rodrigues]

Does it influence the sprints after confirm to save changes to JIRA in advanced Roadmaps.

I'm using JIRA CLOUD, created a ROADMAP and set up some dates, priorities and filter. After confirm to save it in JIRA, I'm not sure and don't understand what has change in JIRA. 

To me the plan in ROADMAP is one thing and JIRA with tickets and sprints is other thing, however that the next sprint don't really need to follow the plan in JIRA ROADMAP.

Other question: When the team planning the next sprint Do they need to plan the sprint with a second screen open in Roadmap, right?

[Walter Buggenhout]

Hi @Renato Rodrigues,

When you change data in advanced roadmaps and then confirm to save those changes, everything you updated in the roadmap will also change in Jira. Usually these will be dates, or maybe the team or release you assigned.

The only situation where you will see immediate impact on the sprint itself, is when you update the sprint your issues are allocated to inside advanced roadmaps. This will add or remove issues from sprints when saving the changes to Jira.

If you want to gain confidence in what is changing, the dialog screen that appears when you click save changes to Jira shows you an overview of the changed fields that will be committed if you choose to continue.

Eventually, it is not necessary for the planning of a next sprint to have a second screen open showing the roadmap. By that, there is no technical reason why you should absolutely do that. However, it is a good idea to review the roadmap indeed before you dive into the sprint planning and specifically pay attention to any alerts it is showing you. That way, you can take any concerns as input into the sprint planning. See the planning of the next sprint as the (very) short term planning, while the roadmap is giving you an insight in the longer term impact of what you are doing today.