Why does keeping a subtask's chat isolated from the main task's chat prevent confusion?

In Jestor, each subtask has its own chat, separate from the main task's chat: a message written inside one subtask doesn't show up if you open another subtask under the same task, keeping every conversation scoped to the context where it was written.

Why would mixing all conversations into a single chat create confusion?

A main task can have several subtasks in progress at the same time, each with a different team or owner. If every message fell into the same general task chat, it would become hard to tell which comment refers to which specific subtask — the relevant information would get lost among conversations from other contexts.

How does chat separation work in Jestor?

Every main task has its own chat, for general discussions about the project as a whole.
Every linked subtask has an independent chat, isolated from the other subtasks and from the main task.
A message written inside a specific subtask only shows up to whoever opens that same subtask.
This keeps information organized: description, notes, and chat, all specific to that card's context.

Level	Chat scope
Main task	General conversation about the project or task as a whole
Subtask	Isolated conversation, specific to that subtask

Why choose Jestor?

This card-by-card isolation adds to other information that's also specific to each subtask — description, notes, and attachments — which keeps the team organized even when several people are working on different subtasks of the same task in Jestor.

Frequently Asked Questions

Can I see every subtask's conversations in one place? Each subtask keeps its own isolated chat; there's no unified view of all conversations at once.

Does this affect mention notifications? Mentions keep working normally within the scope of the chat where they were made.

Does the main task's owner see the subtasks' conversations? They need to open each subtask individually to follow the corresponding chat.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize