The semantic
In the tracker administration (e.g Story)), there is a new option for timeframe semantic: Based on linked artifact (better term to be defined)
We can choose a tracker in the same project (e.g Sprint) that has a timeframe semantic already defined.
The semantic works this way:
- When a Story artifact is linked by one (and only one) Sprint artifact (Sprint is the source of the link)
- And the Sprint artifact has a timeframe defined
- Then the Story artifact timeframe is the same as the Sprint artifact.
If the story is planned in more than one sprint, then we cannot determine the start and end dates: it is considered as an error.
The timeframe of the sprint tracker cannot be removed until no other tracker is based on its timeframe.
A tracker created (duplicated) from the story tracker will inherit the timeframe configuration, except when it is created in another project.
New timeframe configuration is exported/imported in XML and is exposed in the REST API.
When the timeframe is based on another tracker, then the border of the corresponding tasks in the Gantt chart of the Roadmap widget is dashed instead of solid.
Usage in templates
In our existing templates (Scrum & Agile ALM)
- Progress semantic should be set on Stories and Epics tracker (remaining_effort & initial_effort)
- Inherited Timeframe semantic should be set on Stories (-> Sprint)
- Timeframe semantic should be set on Sprints and Releases