Story Editor

Understand the actions, fields, and tools available inside a Story.

Opening a Story from the Backlog brings the Story into focus while keeping the surrounding project context visible.

The Story view gives you one place to review the Story details, update its workflow, manage related work, and collaborate with your team.

Story header

At the top of the Story, you can see the Story ID, Story Type, and title.

The header also includes actions for:

  • Share: Share the Story with someone else.
  • Duplicate: Create a copy of the Story.
  • Delete: Remove the Story.

The Story Type can also be changed from the type selector next to the Story ID.

Points and status

The Story controls show its current estimate and workflow status.

  • Points: Set or update the Story Point estimate.
  • Status: See the Story’s current status and move it through the delivery workflow.

For Feature and Design Stories, an estimate is required before the Story can move forward in the workflow.

Story status typically progresses through:

Started → Finished → Delivered → Accepted

If a Delivered Story does not meet its Acceptance Criteria, it can be Rejected and returned for further work.

Owners and labels

You can assign team members to a Story and add labels to provide additional context.

Owners help the team understand who is working on the Story.

Labels can be used to group or identify Stories by product area, topic, workflow, or other project-specific context.

Story description

The main Story area contains the information the team needs to understand, discuss, and implement the work.

For a Feature Story, the description typically includes:

  • Why: Who the user is, what they want, and why it matters
  • Acceptance Criteria: The conditions used to verify that the Story is complete
  • Notes: Additional context, constraints, decisions, or references that may be useful to the team

Acceptance Criteria can be written as scenarios using Given / When / Then.

Description tools

The toolbar above the description provides quick actions for working with Story content:

  • Template: Insert a predefined Story template
  • Insert Code Block: Add a formatted code block to the description
  • Insert Table: Add a table for structured information
  • Copy Description: Copy the full Story description
  • Translate: Translate the Story description into another supported language

Story templates

The Template action lets you insert either a User Story template or a Bug Story template.

A User Story template includes:

Why As I want So that

Acceptance Criteria Scenario: Given When Then

Notes

A Bug Story template includes:

Steps to reproduce Expected Actual

These templates give the team a consistent starting structure while still allowing the Story to be edited freely.

Autosave and real-time collaboration

Changes to the Story description are saved automatically as you work, so you do not need to manually save each edit.

Tracker Boot also supports real-time collaborative editing.

Multiple team members can work in the same Story at the same time, and each collaborator’s name appears next to their cursor so you can see who is editing which part of the description.

History

The History view records changes made to the Story over time.

You can use it to see:

  • Who made a change
  • What was changed
  • When the change was made

This helps the team understand how the Story evolved and provides a record of important edits and updates.

Comments, Tasks, and Blockers

At the bottom of the Story, you can switch between Comments, Tasks, and Blockers.

  • Comments: Discuss the Story with other team members and add relevant context or attachments.
  • Tasks: Track smaller implementation steps within the Story.
  • Blockers: Record dependencies or issues preventing the Story from moving forward. To add another Story as a Blocker, open the Story you want to reference, copy its Story ID, then use your browser’s Back button to return to the Story you were working on and add the copied Story ID under Blockers.

These areas keep discussion, implementation details, and dependencies connected to the Story itself.

Working with the Backlog

When you open a Story, the list that contains that Story remains visible on the left side of the Story view.

Depending on where the Story is located, the left-side list may show Current Iteration / Backlog, Done, or Icebox.

This keeps the surrounding Story context visible while you review or edit the selected Story.

You can also:

  • Reorder Stories within the list to change their priority.
  • Move through Stories with the keyboard using the up and down arrow keys.
  • Open another Story without losing your place using your browser’s Back and Forward buttons to return to Stories you were previously viewing.

This makes it easy to move between Stories, compare nearby work, and adjust priority while staying in the Story view.

Working alongside Tobi

You can also keep Tobi open alongside the Story while you work.

Use Tobi when you want help reviewing, refining, searching, or taking supported actions on Stories.

Next steps

  • Backlog: Creating, prioritizing, and searching stories.