Intermesh / groupoffice

Group Office groupware and CRM
https://www.group-office.com
Other
188 stars 46 forks source link

project tasklist 6.6 #774

Open migoe101 opened 2 years ago

migoe101 commented 2 years ago

Project task lists not visible in Tasks.

ptl2

It would be practical if you could not only create new task lists in a project, but also use existing ones, which can retain their ACL rights from tasks.

tsp1 .

derjoachim commented 2 years ago

Project task lists not visible in Tasks.

This is by design. We have several users who have literally thousands of projects. The list of task lists would get very messy if project task lists were displayed as well.

It would be practical if you could not only create new task lists in a project, but also use existing ones, which can retain their ACL rights from tasks.

If you create a task list within a project, it will only be available for said project, since the ACL for the task list is directly dependent on the ACL of the parent project. If you were to move an existing task list to a project, the ACL would change likewise. Also, tasks normally inherit their ACL from their parent task lists and have no 'own' ACLs.

What is your use case? Is it sharing common task among similar projects?

migoe101 commented 2 years ago

I am interested in the overall view per employee, per project manager and for the boss. With the filters there is a powerful means to hide superfluous information.

This is also necessary for the address books in one of our projects, since customers are involved and many address books are required due to the ACL. Customers know this way of working today so from O365 and demand more and more. We have quite a few entries in address books, task lists and notebooks anyway.

From my point of view, one system should lead, and for tasks, the task module lends itself to this. See also my comments on Kanban, for my understanding this could be more another "view" for tasks, one or more task lists can be displayed in one or more boards. Owner of the tasks should always be the task list.

For example, with 50-60 projects per project manager per year, 1-10 of them at the same time and between 1-5 employees per project.

For the project manager there is no possibility to see all open tasks on all projects. Likewise, it is not possible for a boss to see the tasks of the entire company. Most importantly, each employee cannot see all their open tasks.

Also, the task list in the project lacks all the nice filters of the task module as well as import and export function.

Tasks are often used not only for real detailed tasks but also for milestone or deadline control. With good categories a nice means of overall control, even more so since the new task module with the possibility to specify not only from to but also the time spent.

Maybe it would be an idea to have projects create new task lists in the task module and have an option to set them to "not visible" for those who mind. Also ACL could still be controlled by the project, in the file module it is the same with the project folders.

So no one is disturbed and who wants can build a complete view.

migoe101 commented 2 years ago

In the meantime I have come to further testing. I found out that sync via CalDAV and ActivSync is also possible for KANBAN and Project Task.

Also the filters do not distinguish between the modules.

For me actually one more argument to make the task module the lead and also to have all tasks in one place in the WebGUI.

image

migoe101 commented 2 years ago

It would also be nice if you bring back this simple project assignment, via drop down it is much more convenient than afterwards via add link.

image

another argument for treating the task lists in the task module and in the project module in the same way is the better view of the task per side panel.

documents and comments are visible by clicking on them without having to open the task.

image

image