A user story is a tool used in Agile software development to represent the required feature or change from the end-user perspective. A user story consists of :

  • As a (type of user)
  • I want to (what is the action or tool being asked for)
  • So that I can (what is the end goal)

User stories are the result of a clear understanding of requirements, business processes and underlying systems. They are what the development team will use to agree and develop any further resulting technical specifications necessary to configure or develop the app. You can add attachments and collaborate on user stories, and the history of status changes is tracked.

Article outline 

  • Creating user stories
  • Change grid behaviour
  • Right panel and adding additional information to a story 

Creating user stories

Stories, ideally, should be added in the context of a "requirement". You can add one or many in the right panel of a requirement in the STORIES tab. 

Or you can switch to the stories list and add them there. You will be able to choose the parent requirement for a story if you want one (not mandatory - but you can add the relationship at any time.).

When you add a story you enter a "summary". Next, follow the standard agile structure of “as a [role], I want to [action], so that I can [outcome]". You can also capture and collaboratively develop the Acceptance criteria for the User Story during the analysis and development lifecycle.

The “as a” is a drop down list of the resources in the Space. There is a Resource Library which can be created and maintained in the Space management app.  You can add tags from existing tags or add new ones to filter stories on. 

Releases are available if you are using Release and Version Management.

Change grid behaviour

The change grid allows you to filter and sort stories by any standard and custom field. You can also resize the column widths. The system will remember all your settings (filters, sorting, column widths) so when you visit the change grid next time it will be exactly how you left it !

In order to edit items in the grid you need to use the command column on the left. The reason is that when you start editing a story we 'lock' it from being changed by anyone else in the system. 

You can also use the context menu (right-mouse click) to delete an item in the grid, edit it, add an attachment or link or copy a link to that item (more on that later in this article).

You can also export all stories visible in the grid (based on applied filers) either in a csv file (which only includes the standard fields) or an excel file (which also includes the custom fields).  You can import stories via csv file as well.

Right panel: Edit, Status, Attachments, Feedback and History

By clicking on the blue arrow button you can hide/open the right sidebar for a story. You can link additional information, such as rich text notes, url links, data tables or images :

You can also collaborate using comments with @mention functionality in the feedback tab:

And check the status history of the story:

You might also find these articles helpful:

Did this answer your question?