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:

Article outlineĀ 

  • Prerequisites

  • Creating user stories

  • Editing stories

  • Change grid behaviour

  • You might be also interested in

Prerequisites

  • Viewer rights to a Space, or

  • Viewer rights to an Org model, or

  • Viewer rights to Reference model

Creating user stories

Stories, ideally, should be added in the context of a "Business 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.

Finally, you can also switch to stories view in the change grid.

Editing user stories

You can edit user stories either directly in the list (right-clicking on an item in the grid) or from the right panel.

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 use the "Documentation tab" in the right panel.

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!

TIP The application does not store sorting information

You might be also interested in

  • JIRA integration - you can connect your Elements Space with multiple JIRA projects in multiple domains and send stories for development

  • Business requirements - business requirements are a tool for documenting your business needs for driving higher value in your company

  • Managing process change with requirements and stories - you can easily raise requirements and stories from the diagram activities. You can also see the status of requirement and story implementation for each activity

  • Sharing requirements and stories - in order to share a requirement or a user story with other users and collaborate on it, you need to copy a unique URL from the Share tab

Did this answer your question?