Comments & Mentions

Collect mentions, unresolved threads, decisions, and replies across project work so nothing important disappears in comments. The screen connects Mentions and Assigned so product teams can find the “New thread” action while checking unresolved and mentions.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Billing migration · Maya mentioned you and Roadmap review · Decision needed, rather than an empty visual shell.

Comments & Mentions
Use this template in Figr

Template facts

Screen

Inbox

Primary action

New thread

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “New thread” action without losing sight of unresolved, mentions and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New thread is clearly available where the task happens.
  • Main view: Mentions keeps the starting point obvious.
  • Connected view: Assigned supplies nearby context.
  • Metric: Unresolved is visible with a meaningful value.
  • Another signal: Mentions helps people judge what to do next.
  • Representative record: Billing migration · Maya mentioned you makes the example specific.
  • Second record: Roadmap review · Decision needed shows the pattern works beyond one item.

States worth designing

  • Inbox empty after filters; show what people can do instead of leaving a blank panel.
  • Loading mentions without changing the layout unexpectedly.
  • Attachment or reply failed; explain the problem and preserve work.
  • Permission denied for assigned; clarify who can continue.
  • Success after choosing New thread; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Mentions → Assigned → New thread → Review outcome

Patterns used

Inbox, Mentions, Assigned, Threads, accessible states, contextual actions

Why these choices work

Keep the active record close to its history, owner and status. Make urgent items easy to find without hiding the rest.

In this design, people should be able to compare Billing migration · Maya mentioned you with Roadmap review · Decision needed. Make unresolved clear, then use mentions to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New thread” action. The happy path alone is not enough.

Related UI examples: Docs Workspace, File Review, Team Calendar.

Start from this in Figr

Design a comments & mentions screen for our existing software product. Use our real design-system tokens, components and product language. Show Mentions and Assigned, include believable records such as Billing migration · Maya mentioned you, and make new thread easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr