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
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.
Auto-Fill Dev Project Field
When you have one active Jira project connected in Elements, we auto-fill the Jira dev project field with the 'Connection Name' value you set in your project setup.
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
Change grid behaviour is covered in this support article.
Main use-cases
Identifying Detailed Needs: User stories are typically more specific and focus on the end-user's perspective. They help in understanding the detailed functional requirements and the context in which they will be used. For instance, 'as a user, I want to filter products by category so that I can easily find what I'm looking for.'
Identifying impact on the system: Elements stories are unique in that they can be linked to process diagrams and components within metadata dictionary, therefore helping to understand impact on existing architecture, business processes, user journeys and features.
Automating governance: Elements stories come with automation that help plan their delivery. For instance, whenever a story is linked to metadata, even at a planning stage, Elements can detect potential future conflict with other stories that share the same component in their scope.
Guiding Development and Testing: User stories are a fundamental tool for developers and testers. They define what needs to be built and provide the criteria for how its functionality will be verified.