Project Roadmap nesting

Question

Hi all,

I've created a roadmap in Project, using several project plans in the online environment. I'm able to get the tasks I want to show on the roadmap. However, main tasks and their nested task are placed in strange locations.

I would expect a main task to always be on top in reference to its nested tasks. In my case nested tasks are sometimes shown higher in the list than the main topic, which IMO screws up the overview. Mostly it's tasks later in the timeline, although I've also seen that it can happen with the first nested task. I also can't find any way to control where a task is located vertically within its own project grouping.

Is there something I'm doing wrong or is this as designed?

I've placed a redacted screenshot here showing some examples of this behavior. The first letters of the tasks are visible to show what belongs together.

Answer 1

Hi Marc,

Thanks for posting in the community. We are happy to help you.

I understand the inconvenience you are experiencing. Per your description, you created a Project roadmap and connected some tasks from other projects. Could you please share a full screenshot of the connected project containing the nested tasks and the main tasks (not the roadmap)? This can help us to better understand the situation. You can upload the screenshot via "Insert Image".

![](https://learn-attachment.microsoft.com/api/attachments/c7f35f31-599c-48cf-aa0f-d7a63526a5cc?platform=QnA

Answer 2

Hi George.

Sure, no problem. Please see the image below. I've inserted the roadmap image as well. This project corresponds with the project shown at the top of the roadmap.

Yesterday the image insertion kept failing, that's why I used the imgur link. For some reason it works now.

I hope this clarifies things.

Answer 3

Hi Marc,

Thanks for posting back and providing the detailed information.

Based on my test, I can reproduce the same situation. When connecting to a project and checking the related Task options to display the tasks, sometimes the Roadmap fails to arrange the main tasks and subtasks in the expected order.

In this case, I think you want all subtasks to be located under the corresponding master task, just like the order in the Project Timeline view.

If my understanding conflicts with your meaning, please point it out and let us know.

If so, I suggest you try the following steps to redisplay the tasks and see if they are in the expected order.

1. Remove the "problematic" subtask phases in the roadmap

This does not delete the related tasks in the project, it just removes them from the roadmap view.

In the roadmap, click on the subtask, in the Phase dialog box, click "Open details". In the Phase pane, click "Remove phase".

2. Show the subtasks again

Click on the row> Details> Update items> check the related task options to show these subtasks again. After a few attempts, the main tasks and subtasks should be in the expected order.

We look forward to your response. Thanks for your cooperation. 😊

Sincerely,

George | Microsoft Community Moderator

Answer 4

Hi George,

Thanks for your efforts so far.

First off, your understanding the issue is correct.

I had already tried some things like switching a single task, or several tasks, off and on again. Sometimes it gives a good result for one of the tasks, but never all. I suspect it has something to do with the available space in the timeline.

For instance: the task starting with P at the top will always insert at that location. It doesn't matter what sequence of removing and re-adding I do, it always pops up at the top. I would like to have it at the bottom underneath its summary task and next to its predecessor.

Since your proposed solution doesn't work consistently; is there any kind of structural solution, or should this be marked as a bug? If a bug, how is that transferred to the PO and devs?

Answer 5

Hi Marc,

Thanks for posting back.

I understand the inconvenience you are experiencing. I've done a lot of searching and testing but haven't found any good solutions. Since I can reproduce the same situation, I think it is a problem with Project Roadmap. In this case, I recommend you report the issue to Microsoft by the following methods. A lot of the features are fixed and improved based on customer feedback.

1. Use the in-app feedback tool to send your feedback for Project: Click the feedback button on the right-up corner of Project > Click I don’t like something to report the issue:

![](https://learn-attachment.microsoft.com/api/attachments/d36b3099-892d-4719-83fb-d11ba296b8ba?platform=QnA"2">