What is a Story?
...
Stories are the basic building blocks of a map that describe something you can deliver and evaluate. Stories on the
...
Story Map are treated as a Story issue type in Jira.
Stories are created under swimlane mode either under Release or Sprint.
...
Created Story “Test Story”
...
Open the editor dialogue by clicking on the card number i.e., EC-189.
The above editor is explained below with all fields:
Epic ID is mentioned with the story that is clickable if user wants to go & check the epic
Description - Add a description of the created story.
Status of the story
Activity options contain filters for showing comments, history, time logs, or all three.
The field is present to add comments by any viewer on that card
The eye icon shown on the top right is showing the viewers on the card.
Vote option is also present for the story
Share the story with any team member
Users can also copy the story link by clicking the link icon near the story ID mentioned at the top of the dialogue box
Few settings for the story 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 story (issue type) as either an XML document or a word document.
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 issue type (story), Epic Link(if it is a step/epic then similar name as the card name, else it would contain an epic name for any other issue type), Fix Versions, Automation, User Story Board WBS Gantt Chart.
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.
There is also an option to change the issue type.
Users can also add attachments for the story, Attach button available, Create a subtask button for creating a subtask. 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.
...
How to create a Story?
To create a Story, go to the portion of the Story Map where the stories are displayed. Hover your mouse over the stories, and click on the + button that appears above or below the other stories.
Then filling the details to create a new story:
Story name
Template for creating a story
Choose the Issue type for the story
Users can change the default issue type for the story by accessing the Admin Settings.
Users also can add the issues from the Issues without epics option from the board menu.
Details that are displayed on the story card at the Story Map are:
Story name
Priority
Story points
Story issue key
Status
Assignee
Child issues (subtask)
Users can also change Priority, Story points, Status, and Assignee by clicking the icons shown on the story card.
Decide which fields to be shown by going to Admin Settings.
How to create a sub-task?
Click on the Child Issue field on the story card to view the subtasks.
Hover your mouse over the subtask, and click on the + button that appears above or below the other subtasks to create a new one.
Click on the up arrow button to collapse the subtasks.