Epics and stories can be configured to work with your own workflow, or SBM Process App.
State transitions are defined by the workflow.
Epic and Story states are workflow states. SBM states can be mapped to Agile phases.
By default, Development Manager Epics and Stories are configured as Dev Change Requests.
The epic and story property definitions are stored in the following XML file.
<tomcat home>\webapps\alm#agile\WEB-INF\classes\story.properties.xml
In the story.properties.xml
under:
<solution>
<type-name>EPIC</type-name>
specify the process app, update transition, and submit transition as shown in this example:
<external-tool-type>SBM</external-tool-type>
<unique-name>your-process-app-name</unique-name>
<update-transition>your-process-app-update-transition</update-transition>
<submit-transition>your-process-app-submit-transition</submit-transition>
</solution>
Make sure the project hierarchy tags point to the epic project in your process app. For example:
<projects>
<project>
<project>your-project-name</project>
</project>
</projects>
TIP Open your process app in SBM Composer and select the transition you want to map in the workflow. In the Property Editor, click General and use the Internal name in the corresponding transition in the XML file.
You can also map priority and story points, which are shown in a header on the form.
An epic is simply a special kind of story. Therefore, it does not have a separate process app. However, it does have its own project within the Story process app. This example shows mapping the Epic Overview UI report to the IDM project. This assumes that the project information has already been configured in the story.properties.xml file.
From the native SBM interface, select the project for which you want to display epics in the UI. For example, IDM Project.
Click Reports.
Create a new report.
Set the Report Project to IDM Project.
Click Save.
Set the Report Title to DVM.View All Epics.
Set Privilege Category to User.
Click Finish.
Modifying the Story mapping is similar to modifying the Epic mapping, except that you change the tags <story-context> under <type-name> STORY.
To make the Story Panel and Epic Overview panes work properly, you need to configure the reports. The reports show the columns you want to show in the UI.
For example, IM Project has columns selected to display:
Issue Id
Summary
Owner
State
In the <view-report> section, specify the report reference name and title for each of the UI elements.
For example, replace the default reports with your process app's reports:
<view-report>
<report-view-all-reference>DevCR.View.All</report-view-all-reference>
<report-inbox-projectparm></report-inbox-projectparm>
<report-inbox-title>DVM.MyWork.Inbox.DevCRs</report-inbox-title>
<report-inbox-reference>DVM.MyWork.Inbox.DevCRs</report-inbox-reference>
<report-view-all-projectparm>F_TS_ASSOCIATED_PROJECT</report-view-all-projectparm>