Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Steps:

Steps are the lower levels defined under Goals. create the backbone of the map by telling the story or narrative of the user’s journey. Steps map with Epic in Jira.

How to create a Step?

To create a step, go to the portion of the user story map where the goal is displayed. Click on the “+” button with a goal.

Details that are displayed on the step card at the user story map are:

  1. Title of the step/epic

  2. Issue link - epic link (step link)

  3. Priority of the step/epic

  4. Status of the step/epic

  5. Assignee

Users can also change “Priority”, “Status“ and ”Assignee” from clicking the icons shown on the step card.

Click on the Epic issue link for adding details for the step/epic.

Details are shown on the editor for the newly created step.

The above editor is explained below with all fields:

  1. Description - Add a description of the created step/epic.

  2. Status of the step/epic

  3. Activity options contain filters for showing comments, history, timelogs, or all three.

  4. The field is present to add comments by any viewer on that card

  5. The eye icon shown on the top right is showing the viewers on the card.

  6. Vote option is also present for the step/epic

  7. Share the step/epic with any team member

  8. Users can also copy the step/epic link by clicking the link icon near the step ID mentioned at the top of the dialogue box.

  9. Few settings for the step/epic are also present that contain adding a flag, connecting to a slack channel, converting this issue type to a subtask, moving this step/epic, cloning this issue type, action menu, printing this page, exporting this step/epic (issue type) as either an XML document or a word document.

  10. Other details for an epic/step are shown on the right side of this dialogue box. It contains the assignee name, Reporter (by default, the reporter is the creator of the issue type), Development branch name (if already created, & option to create a new branch on GitLab or bitbucket), Releases, Labels for the step/epic, Priority, Start Date of the epic, Epic Name (if it is a step/epic then similar name as the card name, else it would contain epic name for any other issue type), Automation, User Story Board WBS Gantt Chart.

  11. There are a few additional fields under the details of an issue type that includes Story Points, Original estimate, Time remaining, Components, Sprint, Fix Versions, and Due Date.

  12. There is also an option to change the issue type.

  13. Users can also add attachments for the step/epic, Attach button available, Create issue in epic button for creating an issue in a step/epic. Issues can also be linked to any confluence document or any link by clicking on the Link issue button. There is a button Show dependency links between issues that show if there is any other issue type task, epic, bug anything dependant (both predecessors & successors) on this card.

Below is an example of a step that is having all the necessary details from a project.


  • No labels