User Stories
To Sync user stories using an ALM integration (e.g., JIRA), follow these steps:
1) Navigate to the User Stories section under Change Management.
2) Click the Sync User Stories option from the User Stories screen. The user stories from the external system will be synced and displayed in the User Stories screen.
3) Click OK. The user stories created in the external system will be synced to ReleaseOwl and will appear on the User Stories screen.
4) To view previously performed sync actions, click on Sync History.
Creating User Stories Without ALM Integration
To create user stories manually for systems not integrated through ALM , follow these steps:
1) To create a new user story manually, click the Create New User Story button.
2) 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.
3) The user story gets created and gets listed in the User Story grid.
4) You can delete user stories by clicking the Delete button.
5) 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 Filter
The Validation Status shows the current stage of the user story validation process. The possible statuses are:
Not Validated: Validation has not yet started for this user story.
Started: The validation process has been initiated.
In Progress: Validation is actively running and not yet completed.
Success: Validation is completed successfully without any errors.
Review Pending: Validation is completed, but the results are awaiting manual review.
Review Completed: The validation review has been completed and closed.
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.
6) When you click the Action button, you will see the list of available actions that can be performed on the user story.
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.
Delete
You can delete the existing user story.
7) The Validation Report will look as follows:
8) On clicking the Pipeline Activity, you can view the release pipeline execution status as follows:
9) Options in Pipeline Activity Screen (Right Panel) The right side of the Pipeline Activity screen contains the following options:
Abort: This button allows users to stop a currently running pipeline activity. When clicked, a confirmation popup appears where the user must provide a reason to proceed. Once confirmed, the pipeline status changes to Aborted for the respective task.
If a deployment is already in progress, selecting Abort will not stop the ongoing deployment. Therefore, the Abort action should be used only when the pipeline is in a Waiting for Approval or Suspended state.
The Pipeline Stage and Pipeline Status of the related user story are also updated to Aborted.
History:
This option displays the execution history of the release pipeline, including details such as the number of times the pipeline was executed, who triggered each execution, and the status of each run.
When you click on the arrow button (>), you are taken to the Pipeline Activity screen.
Refresh:
This button allows you to update the Pipeline Activity screen with the latest information. When you click on the Refresh button, it reloads the current status of the release pipeline to reflect any recent changes or updates.
Release Audit Report
You have the option to export the details as a Release Audit Report. 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:
Release Summary
A high-level overview of the release associated with the user story.
Stage-by-Stage Deployment Details
Detailed deployment information for each stage of the pipeline.
Code and Artifact Changes Summary
A summary of the changes made to the code and associated artifacts, ensuring clarity on what has been modified.
Traceability Matrix
Links between:
Requirements
User stories
Code changes
Deployment stages
This ensures end-to-end traceability for audit and review purposes.
Approval and Audit Summary
A comprehensive summary of:
Approvals obtained for the user story.
Audit trails detailing all actions taken.
Last updated