Create & Manage User Stories
Last updated
Last updated
The Requirement Management module in simplifyQA allows users to create, manage, and track User Stories. A User Story is a short description of a functionality or requirement written from the perspective of the end user.
In simplifyQA, User Stories are connected to Epics and Features, helping teams break down large features into manageable pieces.
To create and delete User Story in the Requirement Management module, the user must be granted the appropriate These permissions are required to perform these actions.
Add a new User Story
From the User Navigation Panel, go to the Requirement Management Module.
b. Click on the “+ Create” button at the top of the Requirement Management page.
c. In the dropdown menu, select “Create User Story”.
d. A form will open for you to fill out the User Story details.
Fill out the User Story details
Fill in the following mandatory fields in the User Story form:
Name: Provide a descriptive title for the User Story.
Assignee: Assign the User Story to a team member.
Acceptance Criteria: Define clear acceptance criteria to specify when the User Story will be considered complete.
Estimated Effort: Specify the effort required to complete the User Story in either story points or hours.
For better traceability and organisation, it is recommended to fill out the following fields:
Epic: Link the User Story to a relevant Epic.
Feature: Select the associated Feature, if applicable.
Release: Specify the Release in which the User Story is planned.
Sprint: Assign the User Story to a Sprint for tracking progress. If a User Story is not assigned to a Release or Sprint, it is considered part of the Backlog. These backlog items remain available in the Sprint/Release Planning Board for future planning and assignment.
Type: Choose the type of User Story—either Gherkin or Normal.
Module: Module in SimplifyQA is a top-level hierarchy within a project, serving as a common element across various application artifacts. It plays a crucial role in organizing and managing test cases, requirements, and defects efficiently.
Associated User Story: An Associated User Story refers to a user story that is linked or related to another user story due to dependencies, shared functionality, or relevance within the same feature or module.
Impacted User Story: An Impacted User Story refers to a user story that is affected by changes made to another user story.
Deployment Status: Track the deployment status of the User Story.
Attachments: Upload relevant files or documents.
Linkages: Add references or connections to other items in the tool, with a "Know More" link for further details..
After filling in all the details, click "Save".
Viewing and editing a User Story
Navigate to the Tree Panel on the left to locate the User Story under its parent Epic or Feature.
Click on “View Details” next to the User Story to open its details page.
Update any of the fields as required, such as effort, assigned user, or priority.
Click Update to save the changes.
Select the User story you want to delete by clicking on the check box next to the desired User Story and the delete icon will show up next to “+create”
Confirm the action to permanently remove the User Story.