Create User Stories

1) You can find User Stories under Change Management section as shown below:

Note:

a) If the project that you are working with is associated with any external system say like JIRA, and if it has any user stories, they appear in the User Stories screen upon sync’ing.

b) Always remember to sync the Sprints first and then the User Stories.

2) Click Sync User Stories option from the User Stories screen. The user stories from the external system gets synced to the User Stories screen.

Note: On clicking Sync User Stories, records of all issue types of the external integrated ALM project will be synced to ReleaseOwl.

3) Click OK. The user stories created in the external system gets synced to ReleaseOwl and appear in the User Stories screen.

4) You can view the sync actions performed earlier by clicking the Sync History.

5) You can create a new user story by clicking Create New User Story link.

6) Enter the following details and click Save:

Field	Description
Summary	A summary of the user story being created.
Description	A detailed description of the user story being created.
Type	Default type is Story. Available issue types: Story, Task, Sub-task, Bug, Issue, Epic, Incident. Any issue type can be created in ReleaseOwl.
Assigned To	Select the user to whom the user story is to be assigned.
Sprint	The sprint in which the user story will be handled.
Release Version	The version of the release in which the user story will get released.

7) The user story gets created and gets listed in the User Story grid as follows:

8) The following columns are seen for a user story:

Field	Description
User Story	Represents the user story being tracked.
User Story ID	Unique identifier for the user story.
Summary	A brief description of the user story.
Status	Current status of the user story. Status options: To Do, In Progress, QA Ready, Prod Ready, Done
Type	Issue type of the user story. Available types: Story, Task, Sub-task, Bug, Issue, Epic, Incident
External ID	ID of the user story from an external system (e.g., JIRA or ServiceNow), shown if the project is integrated with external systems.
Assigned To	The user to whom the issue type is assigned.
Validation Status	Indicates validation status: Success or Completed with Errors.
Pipeline Stage	Default value is Dev. Updates to the next stage upon each promotion in the release pipeline.
Pipeline Status	Status of the release pipeline execution.
Actions	Actions available for the user story: Edit, Validate, Validation Report, Promote, Pipeline Activity. Note: Promote not available for MTAR applications.

9) The user story gets created and gets listed in the User Story grid as follows:

Action	Description
Edit	To edit a user story.
Validate	To validate the user story.
Validation Report	To view the validation report. Note: This option becomes available once the validation is triggered.
Promote	Triggers the release pipeline associated with the project, as configured in Project Settings.
Pipeline Activity	View various stages, tasks, and execution status of the triggered release pipeline.

10) The Validation Report will look as follows:

11) On clicking the Pipeline Activity, you can view the release pipeline execution status as follows:

Exporting User Story Details as a PDF

You have the option to export the details as a PDF. The exported document provides comprehensive information to help track and communicate the progress of the user story.

The exported PDF provides the following comprehensive information:

1. Release Summary

   • A high-level overview of the release associated with the user story.

2. Stage-by-Stage Deployment Details

   • Detailed deployment information for each stage of the pipeline.

3. Code and Artifact Changes Summary

   • A summary of the changes made to the code and associated artifacts, ensuring clarity on what has been modified.

4. Traceability Matrix

   • Links between:

     • Requirements

     • User stories

     • Code changes

     • Deployment stages

   • This ensures end-to-end traceability for audit and review purposes.

5. Approval and Audit Summary

   • A comprehensive summary of:

     • Approvals obtained for the user story.

     • Audit trails detailing all actions taken.

Deputy Users

Deputy users can manage tasks when the primary user is unavailable.

Assigning Deputy Users

1. Click on your profile icon in the top-right corner and select Profile.

1. Click on the Deputy Users tab next to "Projects."

2. Click the Add button, and a pop-up screen will appear.

1. Select Project & User:

• Select the project for which you want to assign a deputy.

• Search for the User in the system and select them.

1. Click the Create button to assign deputy permissions to the selected user.

When a user story is promoted, the assigned Deputy User will receive an approval request. The Deputy User can then navigate to the My Tasks section and go to the Tasks tab. In the Action column, they can choose to Approve or Reject the request.

When you click on the Approve/Reject button, a detailed view will appear, displaying relevant information about the user story. The Deputy User can review this information before making a decision to approve or reject the user story promotion.

When the task is approved, a confirmation message will appear. In the Pipeline Activity section, you can see the task marked as completed, along with the name of the Deputy User who approved it.

In the Deputy Tasks section, the Deputy User can view the task status, including the task name, reference ID, stage, task type, delivery time, assigned to, and action.

When you check the History in the My Tasks section, you can see a record of all actions taken, including approvals, rejections, and task completions, along with the corresponding timestamps and the user who performed each action.