Why keeping a subtask's chat isolated from the main task's chat avoids confusion

A subtask's chat stays isolated from the main task's chat because each one has its own conversation channel — messages written in a subtask don't show up in the source task's chat, nor in other related subtasks.

Why does this separation make a difference?

When several people are working on different parts of the same project, mixing all the conversations into a single chat creates noise: it becomes hard to tell which message relates to which specific stage of the work.

By isolating the chat per subtask, each owner only sees the messages relevant to what they're doing, keeping the history clean and easy to follow later.

How it works in practice

Open a task's card and click "add subtask."
The subtask created is already linked to the source task, but with its own chat.
Write messages inside the subtask — they stay restricted to that specific context.
To see the main task's conversation, you need to open its chat separately.

Level	Chat
Main task	General conversation about the process
Subtask	Conversation specific to that step

Why choose Jestor

Every task and subtask has its own description, notes, attachments, and chat.
Teams can stay organized without losing information between different stages of a project.
Fully customizable task structure to fit your company's workflow.

FAQ

Can I see every message from every subtask in one place?

Not directly; each chat is specific, so you need to open each subtask individually.

Does this work the same in kanban mode and in the table?

Yes, the isolated chat behavior is the same regardless of which view you choose.

Can a subtask have more than one chat?

No, each subtask has exactly one chat of its own, dedicated to it. Learn more at jestor.com.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How Do You Set a Different Homepage for Each Role as Soon as the User Logs In?

In Jestor, when editing a role, you can paste the link to a specific page (like a dashboard) into the homepage field, so that every user with that role lands directly there as soon as they log in. Why this improves the user experience Without this setting, everyone would land

What's the Access Difference Between a Member-Type User and a Builder-Type User?

In Jestor, a member-type user is meant for anyone who just uses already-configured processes, while a builder has access to create and edit tables, apps, automations, and the account's structure. Why separate these two access levels Not everyone on the team should be able to change

Why Does Grouping Tables and Apps for the Same Process Into the Same Folder Make Maintenance Easier?

In Jestor, grouping tables and applications for the same process into a single folder makes it quick to find everything related to a specific Kanban or flow, saving you from wasting time hunting for scattered pieces across the platform. Why folder organization avoids clutter Just like an unorganized computer desktop,

Can You Duplicate an Entire Application, With All Its Elements, Right From the Action Bar?

Yes. In Jestor, the action bar (opened with Ctrl+K or Cmd+K) lets you clone an entire application, with every element it contains, just by choosing the source app and giving the copy a new name. Why cloning from the action bar is faster Manually rebuilding an app from