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:
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. With Elements, you can add attachments and collaborate on user stories, and the history of status changes is tracked.
- 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.
Finally, you can also switch to stories view in the change grid.
Notes on user story standard fields:
- 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.
You can add further information by clicking on "secondary fields", which will allow you to link to parent requirements, specify acceptance criteria, etc.
You can edit user stories either directly in the list or from the item to which it is linked.
To edit a user story from the right panel, ensure you are in the STORIES tab, select the story you wish to edit, and simply click on "Edit story".
To edit a story directly in the list, use the context menu by right-clicking on the target story in the grid:
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 can find these functions in the top right of the page as shown below.
You might also find these articles helpful: