Related links and lists for a Story in Agile Development 2.0

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Related links and lists for a Story in Agile Development 2.0

    In Agile Development 2.0, the Story form providesrelated linksandrelated liststhat help you manage and perform key actions on your stories, such as creating scrum tasks, handling dependencies, splitting stories, and converting stories into epics. These capabilities enable efficient story management and alignment with agile processes.

    Show full answer Show less

    Related Links

    • Split Story: Allows splitting one story into two by creating a new story with the same details and moving any incomplete tasks to the new story. This is useful for breaking down large stories. Restrictions apply to story states and original task types.
    • Add Scrum Tasks: Lets you create multiple scrum tasks linked to the current story, which then appear in the Scrum Tasks related list for detailed task management.
    • Convert into Epic: Converts an active story into an epic, cancelling the original story. This is helpful when a story is too large and needs to be expanded into multiple smaller stories. If the story is already linked to an epic, the new epic becomes a child epic of the existing one. The new epic starts in the Draft state.
    • Copy Story: Creates a new draft story by copying details, tests, and tasks from an existing active story, except for stories added from the triage board. Restrictions apply to story states and original task types.

    Related Lists

    • Scrum Tasks: Displays all scrum tasks associated with the story, with an option to create new tasks directly.
    • Prerequisite Stories: Lists stories that must be completed before the current story can be finished, supporting dependency tracking.
    • Dependent Stories: Shows stories that depend on the current story, enabling visibility into downstream impacts.
    • Tests: Adds existing tests to the story, which then appear on the Sprint Tracking tab of the Agile Board once the sprint begins, linking quality checks directly to story progress.

    Practical Benefits for ServiceNow Customers

    These related links and lists empower you to efficiently manage story lifecycle and dependencies within Agile Development 2.0. You can break down large stories, organize work with scrum tasks, track dependencies to avoid blockers, and associate relevant tests to ensure quality. This functionality streamlines agile delivery and enhances visibility into story progress and relationships.

    Use the related links and related lists on the Story form for the actions that you need to perform on your story in Agile Development 2.0, such as adding scrum tasks, dependencies, or splitting the story.

    Table 1. Related links of a story
    Name Description
    Split Story Splits the story into two stories by creating a new story with the same details. Any incomplete tasks from the old story are moved to this new story.
    Note:
    State of the Story cannot be Cancelled or Completed, and the Original task field, if present, cannot contain a non-story record such as a Catalog Task or Defect.
    Add Scrum Tasks Enables you to create multiple scrum tasks for the current story.

    The scrum tasks are listed in the Scrum Tasks related list of the story.

    For more information, see Create multiple scrum tasks for stories in Agile Development 2.0.
    Convert into epic Converts an active story into an epic and moves the story into the Cancelled state.

    If the story that you created is too large, you can convert it into an epic and then break it down into multiple stories.

    • If this story is already associated with an epic, then the story is turned into a child epic for this epic.

      For example, STRY01 is converted to EPIC01. If STRY01 was associated with EPIC02, then EPIC01 becomes a child epic to EPIC02. Otherwise, EPIC01 is created as a standalone epic.

    • The state of the newly created epic is automatically set to Draft.
    • The canceled story is associated with the newly created epic.
    Copy Story Copies the details of an existing active story to a new story. The tests and tasks of the story are also copied.

    The state of the newly created story is automatically set to Draft.

    This action is not available for stories added from the triage board.

    Note:
    State of the Story cannot be Cancelled or Completed, and the Original task field, if present, cannot contain a non-story record such as a Catalog Task or Defect.
    Table 2. Related lists of a story
    Name Description
    Scrum Tasks Lists the scrum tasks created for the story. Click New to create a scrum task.

    For more information, see Create a scrum task for Agile Development 2.0 stories.
    Prerequisite Stories Lists the stories that must be completed before the current story can be completed. Click Edit to add prerequisite stories.
    Dependent Stories Lists the stories that depend on the current story. Click Edit to add dependent stories.
    Tests Adds existing tests to the story.

    These tests are also listed on the Sprint Tracking tab of Agile Board after the sprint of this story starts.