All Collections
Backlog Management and Spec Editor
Using Stories (formerly: Sub-Features)
Using Stories (formerly: Sub-Features)

How to create, edit and manage Stories in

Maayan Ayalon avatar
Written by Maayan Ayalon
Updated over a week ago

Introduction's workspace has the hierarchy of Product > Epic > Feature > Story. Stories are optional to use. If you haven't already done so, we'd recommend checking out this article to understand's data model in more detail.

All terms can be fully customized from Workspace Settings > Terminology to best fit your use case.
Stories are the smallest parts of your product, here you can list the actual action items in a checklist format. The following article describes the story characteristics and usage:

  • Stories inherit their parent's Objective, Key Result, Release and Sprint, but this can be changed later on a story level if needed.

Creating and editing Stories

From the feature panel click '+ Story':

Create as many stories as you need. To open a story in full edit mode click the arrow icon which appears when you hover the cursor over stories.

Managing your Stories

Once you open the property panel, you may update the Story Status, Assignee, Release, Sprint and OKRs, as well as the Custom Fields. You can Create dependencies, attach files and sync the Story to your dev tool. For more about the Properties panel go to this article.

Viewing Stories in Table view

By default, stories are filtered out from the Hierarchy. In order to include them, go to the Hierarchy filet button, toggle on the Flexible Hierarchy and choose the Story level items.

Read more about the Table View here.

Did this answer your question?