# How to set thread status in Mattermost (To Do / Waiting / Resolved))

**URL:** <https://forum.mattermost.com/t/how-to-set-thread-status-in-mattermost-to-do-waiting-resolved/25851>\
**Category:** Uncategorized\
**Created:** [April 18, 2026, 9:26am UTC](https://forum.mattermost.com/t/how-to-set-thread-status-in-mattermost-to-do-waiting-resolved/25851 "2026-04-18T09:26:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sapl](https://avatars.discourse-cdn.com/v4/letter/s/9de053/32.png) [@sapl](https://forum.mattermost.com/u/sapl)\
**Post date:** [April 18, 2026, 9:26am UTC](https://forum.mattermost.com/t/how-to-set-thread-status-in-mattermost-to-do-waiting-resolved/25851/1 "2026-04-18T09:26:42Z")

</div>

Hi,

Is there a way to mark a thread in Mattermost with a status like:

- To Do / Needs reply
- Waiting
- Resolved

Right now I only see unread/followed, but that doesn’t really help track what actually requires action.

How do you usually handle this?

---

<div class="post-metadata">

**Author:** ![gopi](https://avatars.discourse-cdn.com/v4/letter/g/7cd45c/32.png) [@gopi](https://forum.mattermost.com/u/gopi)\
**Post date:** [April 18, 2026, 11:06am UTC](https://forum.mattermost.com/t/how-to-set-thread-status-in-mattermost-to-do-waiting-resolved/25851/2 "2026-04-18T11:06:15Z")

</div>

No — Mattermost does **not have built-in thread status (To Do / Waiting / Resolved)**.

---

<div class="post-metadata">

**Author:** ![lvovich](https://avatars.discourse-cdn.com/v4/letter/l/e9a140/32.png) [@lvovich](https://forum.mattermost.com/u/lvovich)\
**Post date:** [April 18, 2026, 11:36am UTC](https://forum.mattermost.com/t/how-to-set-thread-status-in-mattermost-to-do-waiting-resolved/25851/3 "2026-04-18T11:36:22Z")

</div>

Yeah, this is a real pain point — especially for tech leads / admins.

We’ve tried a few conventions in teams, but none of them are perfect:

- ✅ — thread is resolved (so we don’t come back to it)

- ⏳ — waiting / needs reply / still in progress

It helps a bit, but doesn’t really solve the core issue:  
you still have to jump across channels and manually track things.

Also: statuses are not always set consistently, they can become outdated after new replies, people forget to update them

What actually helps the most in practice is communication discipline:

- one question / task = one thread
- always reply inside the thread (not in channel)
- avoid mixing topics

Without that, any “status system” quickly falls apart.

---

<div class="post-metadata">

**Author:** ![alex\_lukon](https://avatars.discourse-cdn.com/v4/letter/a/c5a1d2/32.png) [@alex\_lukon](https://forum.mattermost.com/u/alex_lukon)\
**Post date:** [May 10, 2026, 12:10pm UTC](https://forum.mattermost.com/t/how-to-set-thread-status-in-mattermost-to-do-waiting-resolved/25851/4 "2026-05-10T12:10:27Z")

</div>

Funny enough, I ended up building a bunch of workarounds for this too 😅  
Eventually I switched to using **ThreadDesk** (Self Hosted UI wrapepr for MM)

The main thing missing in base Mattermost for us was proper thread statuses + automatic tracking of unanswered threads, so nothing gets lost anymore.

It also has MCP support for AI agents, which turned out to be surprisingly useful.