GitScrum / Docs
Available for VS Code, Cursor, Windsurf, and any VS Code forkInstall from Marketplace

User Stories

Browse and manage your product backlog directly from your code editor. User stories represent features from the user's perspective, with acceptance criteria, linked tasks, and analytics.

The Problem This Solves

User stories live in the product backlog, but developers implement them in the code editor. Switching between the two to check acceptance criteria, review linked tasks, or update story status interrupts coding flow.

GitScrum Studio puts the entire user story workflow inside an editor panel. Read acceptance criteria while coding. Check linked task progress without opening a browser. View the Kanban board filtered to a specific story.

What You Are Looking At

Click User Stories under the Plan section in the sidebar tree. The panel opens with a list of all user stories in the active project.

Story List

The list view shows all stories sorted by date or title. Each story entry displays:

  • Title — The story name
  • Status — Current workflow state
  • Progress — How many linked tasks are completed
  • Story points — Effort estimation (if assigned)

Search: Type in the search field to filter stories by title.

Sort: Toggle between ascending and descending order.

Pagination: Stories load in pages. Scroll down or click to load more.

Story Detail View

Click any story in the list to open its detail view. The detail view has four tabs:

Board Tab

A Kanban board showing only the tasks linked to this user story. This filtered view lets you see exactly which tasks implement the story and their current status.

The board works identically to the main project Kanban — you can drag tasks between columns, click tasks to open the task drawer, and create new tasks that automatically link to the story.

Team Tab

Shows team members assigned to tasks within this user story. See who is working on what and how work is distributed.

Analytics Tab

Data about the story's progress and metrics — task completion rate, time logged, and effort distribution.

Details Tab

The core of the user story:

Story Structure:

As a [user type]
I want [feature]
So that [benefit]

Acceptance Criteria: A checklist of conditions that must be met for the story to be considered complete. Review these while implementing to ensure nothing is missed.

Additional Information: Description, epic assignment, labels, and other metadata.

Working with the Task Drawer

Click any task within the User Stories panel — whether in the Board tab, details, or linked task list — to open the task drawer. The drawer provides the same full editing capabilities as the main Kanban board:

  • Edit title and description
  • Change workflow status and type
  • Assign and unassign team members
  • Attach and manage labels
  • Set start date and due date
  • Set effort estimation (Fibonacci scale: 1, 2, 3, 5, 8, 13)
  • Manage checklists with items
  • Post and read comments
  • Toggle draft, archived, and blocker flags

Pro Tips (Once You Are Comfortable)

  • Use the Board tab to track implementation progress for a single story. The filtered Kanban view is the fastest way to see what is left to do.
  • Check acceptance criteria before marking implementation tasks as complete. Open the Details tab in a split view next to your code.
  • Story points help with sprint planning. When populating a sprint, refer to story point totals to gauge capacity.

Permissions

The extension respects your GitScrum account permissions:

  • Agency Owners and Managers: Full access to all user stories, analytics, and team data
  • Developers: Can view stories, manage linked tasks, and track progress
  • Clients: View-only access to stories (if granted project access)

How to Report a Problem or Request a Feature

If the User Stories panel does not load correctly or data appears inconsistent, open a support ticket in the GitScrum web application. Navigate to Support Tickets in the sidebar and describe your experience. Include the extension version and editor details.