Relevant Fields in a User Story

Updated 1 month ago by Copado Solutions

A user story layout contains a wide collection of fields and related lists. Here we will describe these fields that will provide value to Change Managers, Scrum Masters or Product Owners when managing user stories:

Information

Fields tied to Copado's functionality:

  • User Story Reference: User story identifier created automatically (not changeable).
  • Project: Project linked to the user story. When the user story gets deployed, the destination org is defined by the deployment flow linked to the project.
  • Release: If the user story is part of a product version/release, it must be added here.
  • Org Credential: The org credential for the org where the changes have been made.
  • Environment: This value is automatically added by Copado based on the selected org credential.
  • Promote Change: If this checkbox is marked, the user Story will be available for promotion.
  • Promote and Deploy:  If this checkbox is marked, a promotion and a deployment will be created with this user story.
  • Base Branch: Git branch from where the feature branch originates. This value is updated when committing in the user story and by default, it will be the main branch of the deployment flow or the base branch of the release linked to the user story.
  • Stop Indexing Metadata: Check this field if you want to stop indexing this user story contained within a project which has the Index Metadata checkbox marked.
  • Exclude from CBM: If checked, the User Story will not be included in the count of user stories ahead and behind in the Branch Management feature.
  • Git Merge Status: The Git merge status of the latest pull request between the feature branch and the destination branch. This value is provided by the Git repository. If there is no value, the Git repository did not provide one.
  • Apex Code Coverage: Coverage of the Apex Classes added or committed within the user story.
  • Last Validation Promotion: Promotion that contains the most recent validation deployment.
  • Last Validation Deployment: Most recent validation deployment for the user story.
  • Last Validation Deployment Status: Status of the latest validation deployment for the user story.

Fields not tied to Copado's functionality:

  • Record Type: You can choose from Bug, Investigation and User Story.
  • View in Git: Link to the feature branch in Git.
  • Sprint: When the user story is planned within a sprint, it can be added here.
  • Status: It defines the current status of the user story. The options include the following: Draft, Backlog, Backburner, Awaiting Approval, Approved, Rejected, In Progress, Ready for testing, Completed and Cancelled.
  • Team: This field contains the team in charge of the user story.
  • Epic: An epic is a large user story that awaits decomposition into smaller stories prior to implementation. If the user story is part of an epic, it will be added here.
  • Theme A theme is a group of user stories which contribute to a common goal. It is the highest level in the user story hierarchy. If the user story is part of a theme, it will be added here. For more information about themes, please click here.
  • Priority: Defines a priority for the user story.
  • Backlog Rank: You can set a rank within the backlog for a user story, so that you can prioritize it when creating or editing it. Another way to change the rank is by using the Work Manager panel for your agile backlog.
  • Parent Epic Title: When adding an epic to a user story, the epic's title will be automatically populated here.
  • Story Points:  A story point is a unit of effort required to complete a task. In this field you can indicate how long it will take you to complete the task in the user story.
  • Owner: This field includes the name of the owner (the product owner or any other business stakeholder who created the requirement).
  • Close Date: If the user story has a due date, it can be added here.
  • Cancellation Reason: Reason why the user story has been cancelled or rejected.
  • Progress: Determines the percentage of the user story that is already completed (available as of v11).
  • Progress Status: Displays a graph with the progress done (available as of v11).

Agile Content

  • Title: Short description of the requirement.
  • As a…: Type of user or role.
  • Want to…: Goal (what you want to achieve).
  • So that…: Reason (why you want it).
  • Business Analyst: Product owner, customer, end-user or any other business stakeholder who can be consulted for further information if needed.
  • Developer: User assigned to the user story for its implementation.
  • Test Script Owner: User who created the test script for that user story. It could be a QA team member, an end-user, a business-user or a developer.

Usually, when creating a new user story we will only fill in a few fields, such as those in the Agile content section and the Status field. We will add the rest of the fields later during the lifecycle of the user story.

Additional Information

  • Functional Specifications: Text field available for more detailed functional information.
  • Technical Specifications: Text field available for more detailed technical information.

Acceptance

  • Acceptance Criteria: Conditions that have to be fulfilled so that the user story is considered as done by everyone. It makes it testable and ensures that the user story can be demoed to users and other stakeholders and released.
  • Acceptance Criteria Status: It indicates whether the user story is done or not.

Definition of Done

  • Documentation Complete: It indicates whether the documentation of the user story is completed or not.
  • Pull Requests Approved: It indicates whether the user story's pull requests pull requests are approved or not.
  • Manual Tests Passed: It indicates whether the user story's manual tests are passed or not.
  • Apex Tests Passed: It indicates whether the user story's apex tests are passed or not.

User stories also include a set of related lists that enrich the available information within the User Story detailed page.


How did we do?