In the process of performing one task, it becomes necessary to form a subtask. Those. a new task associated with the current task. There are no tasks in source selection.
Announcement
Collapse
No announcement yet.
Nested tasks (subtasks)
Collapse
X
-
Espo doesn't have sub-tasks out of the box, and unlikely ever will.
If we develop project management tool, there will be a separate task entity with sub tasks.
- Likes 1
-
Yes, project management would be great!
In principle, to implement the project is not very difficult.
I myself try to implement this by rewriting part of the code in the free extension "Real Estate". For example "Properties"-> "Projects" Even I can do something...
But, the project is a more global task. At the same time, it would be very cool if you can create a "project" on the basis of the "task" and then create project tasks in the project. Thus, the connection between the original task, which will develop into a project, would not be lost.
I do not know the plans of respected developers regarding the introduction of project management
Comment
-
+1 for "project management tool"
but i understand the work for maintain all (code, crm, extension...) .. for only one guy :s
- Likes 1
Comment
-
yuri I'd also love to see project management in Espo. Since you last commented on this more than a year ago, I'm wondering if you have any updates on the idea. Is project management still in the consideration stage or have you decided to move forward with it? I'm asking because we need to do something about PM, but if it will be available for Espo in the near future, I'd rather just wait.
Comment
-
yuri I'm glad to hear this is on your roadmap. When conceptualizing the PM piece, perhaps you'd consider drawing some inspiration from Huly, an open source PM system, currently garnering a lot of attention on Product Hunt. It seems they offer a fresh approach to PM in terms of how the system automatically manages To Dos:
Huly introduces Todo — not as a replacement for Task, but as the actionable end-point of these processes. A Todo is the commitment of an individual to move the needle, an agreement between the team member and the task at hand, personalized and precise. It stands as the final link in a chain of productivity, ensuring that no step is too small to be overlooked and no detail too fine to be refined.
Huly’s intelligence lies in its ability to manage transitions between stages. When a designer marks their Todo as Done Huly understands that it’s time for the Task to move to its next phase. Automations seamlessly create the next set of Todos, pinging the software engineer that it’s their turn to transform design into functionality.
In the Huly ecosystem, processes never grow stale. Should a Todo linger unattended, reminders go out, ensuring that the flow of work continues unimpeded. And if a Todo is canceled, Huly gracefully rolls back to the previous state, finding the next path forward to keep the project on course.
Comment
-
Back to sub-tasks (not PM). Currently, it's possible to create a one-to-many relationship between Task and Task. If we ever implement sub-tasks, I believe this will be that simple: just a relationship. Or no? Does anyone have any ideas what else this functionality could comprise?
Comment
-
Originally posted by yuri View PostThere is a huge number of PM products we could get inspiration from. I don't think we need a solution for software developers but rather more generic one.
Comment
-
I believe the Workflow tool could be potentially utilized for PM automation purposes. E.g. when a Task is finished, a dependent Task assignee receives a notification to start their Task. Or, when a Task from a backlog is changed its status to Ready, move this Task to a Project. Just my ideas.
Comment
Comment