User Manual

Product Owner – User Manual (Version 2.1)

The Story Map plugin is like a „card game“, which has two different card types: Stories and Epics. The Epic is the grouping unit, which contains its appropriate stories. With it the product owner has a powerful tool to manage all requirements even if it is a complex system without losing track of the big picture. It gives him the ability to tell a bigger story and the safety that he did not forget anything. Each card displays a compact set of information. This manual gives the user a detailed description of the provided functionality.
If you have technical questions refer to the installation how-to.

1 The Cards

At the left top of the card the Issue Type is displayed. A Story Map consists of Stories and Epics, which can be grouped and ordered in different ways.
The JIRA ID is linked to the standard JIRA-Issue, which will be shown in a new target window
The Create Story button opens a dialog window to describe a new Story. This newly created Story will be related to the Epic.
The Edit (Story or Epic) button opens a dialog window which allows editing the card.

The Story Point field shows the ‘weight’ of a card. You can edit this field by clicking at the ‘edit’ button. All points of an epic are summed up and shown at the progress bar’s mouse over window.
The More button enlarge the card (only Stories) and let the related sub tasks appear.

The Summary area shows the cards label and can be edited by the edit dialog. The summary is cropped after alilmited number of characters, but the entire text is shown by the mouse over event.
The Progress Bar shows the epic’s progress based on the story points of each related story. Note: The progress bar’s mouse over event shows the story points summed up over all related stories.
The Target Version is the related Sprint, where the story is applied to. This can be edited by the edit dialog and marked by the filter function.
The Status Icon shows the JIRA status, that is configured at the project’s workflow.The Priority Icon shows the standard JIRA priority:

2 Multi Project Map

With version 2.0.3 we added a cross project view. Unfortunately there is no UI to select the desired project but it can be controlled via URL: to include more projects into the same map you have to pass the desired project keys (comma separated, no blanks) via a URL parameter like this:

http://my.jira-host/plugins/servlet/bit/selectedProject.storymap?projects=project1,project2,selectedProject

Make sure that the ‘selectedProject’ is added to the url as well. Then, if you have permission to view them, you will gain a map of stories and epics of different projects. With it you can:
# move and link stories to epics of another project
# create/edit epics and stories on the fly

Constraint: you cannot set versions of a different project. However if you try nevertheless, it will lead into an exception alert.

3 The Tool Bar

# The Zoom slider lets you zoom into and out of the map. It is very useful to visualize even big maps.

# the next button, which looks like an eye reduces the size of all cards

# the cross button ‘Create Epic’ is used to create a new epics. After clicking the edit dialog will appear, where you can name it and define some properties. Finally a new card will be placed at the right side of the map. Then you can start adding stories. Note In case of a cross project map it will create an epic of the project which is the first in the URL

# The Help button links you to this document

# the Feedback button gives you the ability to report a bug, to send a comment or even tell the developers behind that you like the add on

4 Order Stories and link them to Epics

Each story can be moved from one epic to another even across project borders. Just drag and drop it at the desired epic. A grey layer shows where the card will be placed after dropping it.

Within an Epic you can move stories up and down to prioritize it. Epics can be ordered horizontally. This order will be synchronized with GreenHopper as well. After dropping, the story will be saved and the progress bars will be refreshed automatically.

5 The Filter

The left menu item at the navigation bar makes a small window to be faded in. It shows all selected projects (see cross project view) as an accordion. Within a project there are several units: Status, Versions, GreenHopper Sprints and Components.
Each line has a label followed by a progress bar, which shows the share of stories (evaluated with Story Points) related to all stories in that unit. The next check box can be used to hide selected cards at the map: The implemented behavior is:
If the check box is checked, the cards are visible. If the checkbox is unchecked the cards becomes invisible. The radio buttons in front of the colored background are used to mark the related cards by the color of the button. Note: if a card matches two criteria it will obtain it’s color from the radio button, which is been clicked latest.
At this way you can focus on some particular sprints, versions, components and manage your releases.

6 Alerts

Each interaction and each modification will be observed and logged.
If an action was performed successfully, it is confirmed by an alert window.

7 Document History