ReleaseOwl Docs
  • ReleaseOwl Admin Guide
    • General Administration
      • User & Role Management
      • Project Management
      • Landscape Registration
      • Global Credential Management
      • Settings
      • Landscape Connectors
      • Parallel Landscape Configuration
      • Static Code Analysis
      • RO Agents
    • ALM Integrations
      • Jira
        • Jira Cloud
        • Jira On-Premise
        • Jira Automation Rules
      • Azure DevOps
      • ServiceNow
      • Freshservice Integration
    • Other Integrations
      • ReleaseOwl Callout Feature
      • DocuSign
    • Landscape Mapping
  • ReleaseOwl User Guide
    • Change Management
      • Backlog
      • Sprints
      • User Stories
      • Release Versions
      • User Story Dependency
    • Transport Management
      • On-Prem Environment Registration
      • Creation of Transports
      • Transport Validation and Analysis Reports
      • Transport Promotion and Pipeline Activity
      • Transport Management Actions
      • Transport of Copies
      • Retrofit & Conflict Resolution
      • gCTS
        • Build pipeline support for onPrem Fiori
    • SAP BTP
      • Administration
        • Credential Management
        • Cloud Environment Registration
      • Working with Build Pipelines
        • Static Code Analysis
        • Change Log Analysis
        • Download Artifact
        • Labels
      • GIT Ops
    • SAP API
      • Adminstration
        • Credential Management
        • Cloud Environment Registration
      • API Management
    • SAP CPI
      • SAP CPI Integration with ReleaseOwl
      • CPI Test Generator
      • CPI Management
        • Synchronize CPI Artifacts
        • Artifact Versions
        • CPI Artifact Comparison
        • Backup & Rollback
        • CPI Validation - CPILint
        • iFlow Unit Testing
        • Integration Advisor
    • SAP Analytics Cloud
    • SAP Datasphere
    • Working with Release Packages
      • Create Release Package with User Stories
      • Create Release Package with Transports
      • Release Package Validation with Transports
    • Working with Release Pipelines
      • Pipeline Tasks
        • Approval Task
        • Callout Task
        • Manual Task
        • User Story Status Task
        • Test Execution Task
        • Message Listener Task
        • GCTS Merge Task
        • GCTS Activate Task
        • GCTS Switch Task
        • Import via Toc Task
        • Transport Retrofit Task
        • Release Transport Task
        • DocuSign Approval
        • Validation Task
      • Use Cases
        • Automated Transport import along with Transport Promotion
        • Automated MTAR Deployments
        • Automated CPI Deployments
    • Test Automation
      • HCL OneTest
        • Test Configurations
        • Running Automated Tests with Release Pipelines
      • Tosca Integration
      • Integrating UiPath with ReleaseOwl
    • My Tasks
    • Multiverse
    • Utilities
      • ABAP Version Compare
      • gCTS Merge
Powered by GitBook
On this page
  1. ReleaseOwl User Guide
  2. Working with Release Pipelines
  3. Pipeline Tasks

User Story Status Task

PreviousManual TaskNextTest Execution Task

Last updated 7 days ago

User Story Status Task

The status of a user story can be set to a specific value once the deployment takes place in an environment. The following screen is displayed on adding a user story status task.

Fill in the required details:

Name

Enter any name of your choice for the user story status task being created. Note: Only letters, numbers, underscores (_), and periods (.) are permitted.

User Story Status

Select appropriate status to which the current status of the user story has to be changed once the deployment to specific environment is done. The available status options are: To Do – The user story status can be reset to - To Do once the deployment is done in any specific environment. For e.g., the same user story can be deployed to multiple environments one after the other and in each stage the status has to be reset to - To Do as the process has to be repeated. In Progress – The user story status can be set to In Progress when the implementation of user story is still work in progress or done in a phased manner . Ready for QA – The user story status can be set to Ready for QA once the deployment is done in QA and is available for testing. Done - The user story status can be set to done once working with the user story is complete after deploying the changes to the specific environment.

Description

Any message that is to be conveyed to the task performer can be mentioned here.

Continue on Failure

Enable this option if you want the pipeline to proceed with the subsequent tasks even if one task fails. This is useful when multiple tasks are configured in a stage and a failure in one task should not block the execution of the remaining tasks.