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 who benefits from the change)
  • 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
  • Editing stories
  • Change grid behaviour

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.

You can also raise stories directly from the process activities or Salesforce Org Models. While adding the details you can specify the parent requirement of a story being created in the field at the bottom of the modal window.

Finally, you can also switch to stories view in the change grid and add your stories from 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.

Editing stories

Through analysis of how the new story impacts the existing processes or technology, and by consulting with crucial stakeholders, you might discover that a story needs to be refined or enriched with additional information. 

To edit a story and add additional information use either the "Edit" button in the command column on the left or use the context menu by right-clicking on the target story in the grid:

You will have an option of either editing a story in:

  • modal window
  • in-line in the grid
  • or to change the status only in a modal window

In order to attach additional information (images, url links, rich text notes with solutions etc.) or to establish links to other processes activities or technology components again right-click on a target story to access the context menu OR open the right panel by clicking on the blue arrow on the right:

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 your settings (filters & column widths) so when you visit the change grid next time it will be exactly how you left it !

* The application does not store sorting information

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.


You might also find these articles helpful:

Did this answer your question?