Task Object Enhancements — Details & Comments Fields

Overview

The standard Salesforce Task object provides only a Subject field for describing work, which is insufficient for teams that need to communicate detailed specifications, material requirements, or project context alongside task assignments. A two-field enhancement pattern — a Details field for structured specs and a timestamped Comments feed — addresses this gap without requiring a move to heavier objects like Cases.

This pattern was identified and specified during a ^[1] optimization session in March 2026.

The Problem

Out of the box, the Task object's primary descriptive field is Subject — a short text field intended as a title. When a task creator needs to convey rich context (e.g., "Client wants 7'×20'×10" Berry Gray Granite panels, 22,000 sq ft, specific finish"), there is nowhere to put it at creation time. Users resort to workarounds like stuffing details into Subject, using Chatter (which is disconnected from the task record), or communicating outside the system entirely.

A secondary problem: when tasks are assigned to another user, the creator may lose the ability to add follow-up notes due to permission rules that restrict editing records "owned" by others. This creates a situation where the person with the most context about a task cannot annotate it.

The Solution

Add two fields to the Task object:

1. Details (Long Text Area)

• Purpose: Captures the full specification or context provided by the task creator at assignment time.
• Who fills it in: The person creating/assigning the task.
• Example content: "Architect now wants price for 7×20×10 inch panel, Berry Gray Granite, 22,000 sq ft."
• Behavior: Editable by the creator; treated as the authoritative task brief.

2. Comments (Timestamped Feed)

• Purpose: Provides a running log of notes from any user involved with the task — updates, questions, status changes, or clarifications.
• Who fills it in: Any user (creator, assignee, manager).
• Behavior: Each entry is automatically stamped with the author's name and timestamp. Users can add their own entries but cannot edit or delete entries made by others, preserving data integrity.

Permission Model

The Comments field design requires careful permission scoping:

This is distinct from the broader task editing permission, which should allow the creator to annotate a task even when it is assigned to (and therefore "owned" by) another rep. The default Salesforce behavior of blocking edits on records owned by others must be explicitly overridden for the Comments field.

See ^[2] for the broader permission audit context.

Implementation Notes

• Both fields are added directly to the Task object via the Object Manager.
• The Comments feed behavior (auto-timestamp + author name) can be implemented as a custom Long Text Area with an append-only Flow, or via a related custom object if full audit trail is required.
• Chatter on the Task record is not a recommended substitute — it is disconnected from the task layout and not visible in standard task list views.
• The Details field should appear on the task creation screen (New Task modal), not just the detail view, so creators can populate it at the moment of assignment.

Client Context

Identified at ^[1] during a working session with Lincoln Durham and the Asymmetric team (Mark Hope, Karly Oykhman). The specific use case: a sales rep (Tom Proboa) created a task, assigned it to a colleague (Brian Rediman), and then could not add a comment to his own task. Separately, Lincoln noted that the Subject field alone was inadequate for communicating stone panel specifications to the estimating team.

Action items from that session (Asymmetric):
- Add Details (long text) field to Task object
- Add timestamped Comments feed to Task object
- Ensure creators retain comment access on tasks assigned to others

Related Articles

• ^[2]
• ^[3]
• ^[4]
• ^[5]