Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt

Use this file to discover all available pages before exploring further.

Rich item details are what make an item operational instead of decorative. The title and fields give you structure. The item details give you the evidence, discussion, and working context that make the item trustworthy.

​
What lives inside item details

Custory item details can hold:
  • Description
  • Files and attachments
  • Image gallery
  • External links with context
  • Comments
  • Linked items
  • Linked external tasks
  • Item history
  • Pending AI-related activity
The goal is simple: keep the working context on the item that needs it.

​
Why this matters

For smaller teams, the default failure mode is not “we captured too little.” It is “the context is split across five places.” Rich item details help prevent:
  • Evidence living only in Slack
  • Screenshots living only in downloads
  • Reasoning living only in someone’s memory
  • Follow-up work living only in Jira or GitHub

​
Description

Use the description to explain the item well enough that another teammate could act on it without a live handoff. Good description content:
  • What happened
  • Why it matters
  • Evidence or examples
  • Unknowns that still need validation

​
Files and attachments

Attach files when the evidence itself matters:
  • Screenshots
  • Research artifacts
  • Customer examples
  • Exported reports
  • Documents
Attach the file to the specific item it supports, not just to the journey in general. Image attachments are especially useful for:
  • UI friction
  • Customer-submitted screenshots
  • Before and after comparisons
  • Design references
When a problem is visual, keeping the image on the item makes review faster and reduces context switching. Item details support external links with titles and descriptions. Use links for:
  • Call recordings
  • Docs
  • Dashboards
  • Tickets
  • Research notes
  • Support threads
The link matters, but so does the explanation. Add enough context that a teammate understands why the link exists before opening it.

​
Comments

Use comments for the discussion that should stay attached to the work:
  • Clarifications
  • Counterpoints
  • Open questions
  • Decision notes
  • Follow-up observations
This is one of the highest-leverage habits in Custory. It keeps the conversation where the actual item lives instead of splitting it across chat tools and meetings.

​
Linked items

Use item links when the relationship itself matters. Examples:
  • A touchpoint linked to the insight it produced
  • An insight linked to the opportunity it created
  • A solution linked to the metric that will validate it
See Linking items for the full relationship model.

​
Linked external tasks

An item can stay connected to work in external tools such as GitHub, Jira, Linear, and Notion. This is how Custory keeps the customer reason attached to delivery work instead of losing it during handoff. See External tasks and issues for the deeper workflow.

​
History

Item history matters for two reasons:
  • It helps the team understand what changed
  • It makes AI and human collaboration more auditable
Use history when you need to answer:
  • Who changed the status?
  • When did the priority shift?
  • Why does the item look different from last week?

​
Pending AI activity

When AI is involved in work around an item, Custory can surface that activity so the team can see that processing is still in progress. This reduces the common confusion of “did anything happen?” when AI is doing more than instant text generation.

​
Best practices

​
Keep the proof close to the claim

If an item makes a strong statement, attach the proof or source context whenever possible.

​
Use comments for reasoning, not just reactions

Short reactions are fine, but the real value is preserving why the team agreed, disagreed, or changed direction.

​
Update linked tasks instead of rewriting context elsewhere

If implementation work already exists, link it. Do not make the item and the delivery tool drift into separate narratives.

​
Common mistakes

​
Overloading the title because the details are empty

If the title has become a paragraph, the item probably needs a better description and supporting detail.

​
Attaching evidence at the journey level only

Journey-level material is useful, but if the evidence supports one item directly, attach it there too.

​
Treating comments as optional

When the reasoning stays off-item, the next person has to reconstruct it from memory or chat history.