DreamManager is HeroEngine’s integrated, agile bug and task tracking system. It enables HeroEngine developers to create stories, assign them to users, and place them in sprints for tracking to completion.
NOTE: For information on the previous version of Dream Manager, please refer to Dream Manager 1.0
Each world must have a DreamManager configured for it. This is completed as part of server configuration for HeroCloud licensees and HeroEngine hosted licensees. Source licensees can do this themselves via the Master Control Console. To configure a DreamManager for a particular world, open the Master Control Console, and click on the Edit Worlds button.
For more information, see World Editor.
Access to the Dream Manager can be found from the quick access icon on the HeroBlade toolbar, or from the Tools menu. Updates to tasks for the logged in user are displayed next to the quick access icon for a short period of time, and the 8 most recent updates can be accessed from the drop down icon menu.
All users need to have a Dream Manager username to create or modify stories, users, or sprint information. The user will be prompted to automatically create this when necessary if it does not exist.
A user may also create users for other people as needed, i.e.: a team lead might create users for all other team members while setting up stories and sprints. New users can be created using the New User button at the bottom of the Users tab.
By default, all stories go to the backlog, which is the list of all stories which are not currently scheduled in a sprint.
Sprints can be created using the Sprint button at the bottom of the Backlogs page. Each sprint is then displayed using its own tab.
All sprint, backlog, and story data can be exported as a hierarchical XML data file using the Export button at the bottom of the Backlog tab. This allows users to import the data into a management tool or spreadsheet for project planning.
Feature tasks, bugs, and chores are represented as stories. Stories can be created using the New Story button on the Backlog tab, or any sprint tab.
- Title: Title of the story
- Description: Description of the story
- Requested by: User who is requesting the story
- Owner: User who is responsible for implementing the story
- Type: Type of story
- Points: Number of points that the team is assigning to the story. Typically, more complex and difficult tasks are assigned more points. Points may or may not correlate to number of days required to complete the story.
- Priority: Importance of the story. 1 is the highest priority. 3 represents "average", and is the default.
- Severity: Impact of the story. 1 is the highest priority. 3 represents "average", and is the default.
- Links: A story can have multiple links to an area location, GM Note, or Script. Double clicking on the link in the list will take you to the area, GM Note, or script.
By default, a story has not been started. Over the course of creation, development, completion, and acceptance, a user can transition a story from Not Started, to Started, Completed, Accepted, and Delivered. Cycling the status beyond Delivered returns it to Not Started.
Sprints organize stories into groups of related deliverables. Each sprint has a configurable name and start date. The length of sprint is typically proportional to the total number of story points in the sprint. A sprint is considered complete when all stories are Delivered, at which point the story points are deducted from the total. A sprint is considered complete when there are zero story points remaining to be Delivered.
Double clicking on a story will allow the story to be edited.
The New Story button on the sprint tab will add the story directly to the sprint instead of placing it in the backlog.
Stories can be dragged / dropped between the backlog and sprint.
external function SubmitDreamManagerTask(title as string, desc as string, team as string, \ type as string, class as string, urgency as string, parent as string, heat as string, \ linkXML as string, duplicateIdentifyingText as string)
The strings match what is displayed in HeroBlade.
- 'parent' can be either a task title or its number.
- 'heat' is a number from 1 to 10.
- 'duplicateIdentifyingText' is checked against recently submitted tasks to determine if it can be thrown away. If left empty, it becomes a concatenation of 'title', 'parent', 'linkXML', and the current script call stack.
Examples of 'linkXML' are:
// <l name='buena vista' type='Area View' pos='0,0,0' rot='0,0,0'/> <l name='frodo' type='GM Note' note='the ring'/> <l name='something' type='client HSL' script='joshtest' line='1'/> <l name='problem' type='blocked on' task='42'/> //
- World Editor, to show how to configure a specific world to use the DreamManager system via the Master Control Console