Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

New release data structure

Log in to subscribe to topics and get notified when content changes.

New release data structure

New release tables are extensions of the Planned Task table.

Note: Functionality described here requires the Release Management v2 plugin.

New Tables

Each of the different Release Management plugins implements a different set of tables. The tables differ from the old Release tables because they are now extensions of the Planned Task table, meaning they can now use all functionality specific to the Task table (such as Approval and Assignment Rules), as well as the standard time-related functionality provided by Planned Task.

New Table Relationships

The change in the data structure is not limited to new tables. The relationships between the tables are implemented differently, to allow more flexibility. The old tables were separate tables related by a parent-child relationship:
Figure 1. Old Table Relationships
The new tables are now all extensions of the Planned Task table:
Figure 2. New Table Relationships
New table relationships
Individual records can be associated with themselves in parent-child relationships using the Parent reference field available to all of them. However, because the Parent reference field can point to any task, records on the release tables can be associated with any records anywhere on the release table. Therefore, it is possible to have Parent and Child releases and Parent and Child features.

In this example (displayed using the hierarchy view), the Product has Releases is broken up into subreleases, which have child features defined:

Figure 3. Release Management Hierarchy
Release management hierarchy