Change the Task location under a Task Manager page

[AndreeaChi]

There is a current case when importing spaces containing tasks when they are imported as child pages of a parent page. When they are numerous, the navigation panel or page hierarchy can become too large, not very user friendly.

The suggestion would be to combine tasks over under a Task Manager page rather than as the current behaviour.

[DarkJoney]

I would like to say this is a critical flaw, we have stopped all migration processes due to this. Big spaces are wrecked, and navigation does not basically not exist in this form. And I have to find a way how to clean it up myself, because we imported 4GB of space which is a very slow process, and a few huge ones are remaining.

Weren't you referring to the confluence during the programming?

Please combine it under the top-level tree at least for now not to affect actual page navigation. I wish to put the screenshot here, but this is my private github account.

[snazare]

We will add a configuration that will allow the Administrator to choose the location of the task pages created (under the parent page, as it is now, OR under the common main TaskManager page)

[DarkJoney]

@snazare If it would have been under the parent page like you have done with the draw.io it wouldn't be a problem at all. The current behavior is to generate HUNDRED of tasks and slap them to the root of the space making all the navigation unusable. The second option also is not optimal in my opinion. I thought it would be something like SPACE -> TaskManager -> Tasks. If you will put them under the main space, then how are you going to separate them?

Anyway, I just want to have an answer to my colleague that asks about the task lists everyday.

[mflorea]

If it would have been under the parent page like you have done with the draw.io it wouldn't be a problem at all. The current behavior is to generate HUNDRED of tasks and slap them to the root of the space making all the navigation unusable.

@DarkJoney I don't understand what you mean by "slap them to the root of the space". The current (expected) behavior is to create the task pages as children of the page that has the task macro calls. This means that if you have for instance a page "Path.To.Page" with 3 task macro calls then you should normally get 3 task pages:

• Path.To.Page
  • Path.To.Page.Task1
  • Path.To.Page.Task2
  • Path.To.Page.Task3

@trrenty to confirm. Currently, I don't fully understand your problem:

• do you have Confluence pages with lots (e.g. tens or hundreds) of task macro calls, and you don't like that the task pages are created as child pages of the imported Confluence page, because these child task pages are mixed with the other child pages that the imported Confluence page may have?
• you end up with task pages that correspond to different Confluence pages grouped under the same parent? Something like:

  * Parent
    * Task1FromPage1
    * Task2FromPage1
    * ...
    * Task1FromPage2
    * ...
  

Grouping tasks generated from a single page (with task macro calls) under a "Tasks" child sub-page is possible. Such as:

• Path.To.Page
  • Path.To.Page.Tasks
    • Path.To.Page.Tasks.Task1
    • Path.To.Page.Tasks.Task2
    • Path.To.Page.Tasks.Task3