Context

We use ClickUp as an all-in-one app (documentation, task execution, and communication). ClickUp already has Relationships and References (mentions/backlinks), but information is still fragmented across Docs, tasks, and Chat. As the workspace grows, it becomes hard to understand “what is connected to what” around a topic, and where key decisions were discussed.

Problem

There is no unified, graph-style visualization of connections across Docs, tasks, and chat discussions.

Topic-based discussions in Chat are hard to track over time; you cannot quickly see all threads related to a topic, who participated, and which tasks/docs resulted from the discussion.

Decision context gets lost; tasks exist, but it is unclear which conversation led to the decision and why.

Proposed solution

Introduce a dedicated Graph View (Obsidian-style) that shows nodes and edges across:

Docs and Doc pages

Tasks and subtasks

Chat: channels and especially chat threads (threads as first-class, linkable entities)

The graph should reuse existing links and add a small set of missing primitives:

A) Reuse existing link types

Task Relationships: linked tasks, linked docs, dependencies

References/backlinks: generated by @mentions across the workspace

B) Add missing capabilities for “topic-based chat”

Topic linking for chat threads: ability to link a chat thread to:

a Topic entity (new concept), or

a dedicated “Topic” tag/label system

optionally also link the thread directly to a Doc/task (“this thread is about X”)

Goal: make “chats by topic” navigable and durable, not just chronological messages.

Core use cases

Topic map: open a Topic (e.g., “Pricing”, “June campaign”, “Client onboarding”) and see:

related Docs

related tasks/subtasks

all related chat threads where it was discussed

Who discussed it: for every chat thread node, show:

participants (avatars + count, ideally top contributors)

time window (first/last activity)

Decision traceability: go from a strategy Doc to the discussions that led to decisions, and to the execution tasks that implement them (and vice versa).

Find orphan items: identify Docs/tasks/threads with no links.

MVP requirements (minimum viable)

A Graph View available at Workspace/Space/Folder/List scope, plus “neighborhood view” starting from a Doc/task/thread.

Nodes: Doc, page, task, subtask, chat thread.

Edges: existing relationships + references (@mentions) + “thread linked to topic”.

Participant visibility on chat thread nodes.

Filters: node type, edge type, task status, assignee, channel, time range.

Permissions-aware: only show items the viewer has access to.

Click to open: clicking a node opens the underlying Doc/task/thread.

Nice-to-have (after MVP)

Expand neighbors on demand (depth 1-3) for performance.

Activity weighting/heatmap to highlight highly active discussion threads.

“Create task from thread” automatically keeps the graph link.

“Topic page” that acts as a hub (Doc/page with embedded graph widget and linked items).

Acceptance criteria

From a Topic, I can open Graph View and instantly see all related chat threads, docs, and tasks.

I can filter to only chat threads and answer “who discussed this?” quickly.

I can navigate Doc -> thread -> task and back without manual search.

Why this matters

ClickUp already has the underlying relationship data (Relationships + References). A unified graph that includes Chat would turn ClickUp into a true second-brain system where decisions, discussions, and execution are connected and easy to trace.