Managing Release Types
Users who have Manage Release Type permission can access the "Manage Release Types" menu from the top navigation
The Release Types page allows you to perform the following operation on a release type:
Creating New Release Type
Start by clicking on the Create type button. This will open the Create Release Type dialog.
Fill in name and description of your new release type and click Create.
After your new release type has been created you're redirected to the release type configuration page. On this page you can configure:
- General configuration
On this tab you can change the name and/or the description of your release type at any time by editing the fields and clicking Save
You need to click the Save button only if you're changing the release type name or description. Any changes made on Stages, Gates or Approvals tabs are applied immediately.
Stages represent the different phases of your process. To add a new stage fill in the name, description, duration and color and click the Add button.
Duration of a stage is in the format:
number of months m number of weeks w d
You can later change the duration of a stage for each different release.
The color of a stage controls the color which is used when a stage is displayed on a Release Calendar timeline.
A stage gate the transition between two stages. Your process might require certain rules to be fulfilled before a release can transition from one stage to the other, Cycle allows you to define such rules by adding gate conditions and/or approvals. A condition is a rule described by a JQL query which is automatically evaluated by Cycle, while approval is a rule which state is manually set by the user.
You can attach conditions and approvals to each stage gate on the Gates and Approval tabs on the release type configuration page. For each defined stage there is a separate tab (as pointed on the screenshot below) which allows you to add any number of conditions to be evaluated.
The gate condition works by comparing the number of issues returned by the specified JQL query to the specified expected value using the specified operation. For example, if you want to allow transition from Planning stage to Development stage only if there are at least 10 Epic user stories defined in the release, you will have to enter the following values (see the screenshot below)
The JQL query issuetype = Epic will be evaluated on the Release Content and Cycle will check if the number of issues returned is greater than 10 and only if this is true the condition state will be considered as passed.
You can attach any number of approvals to a stage. The effect of adding an approval is that in order for a gate to pass, all approvals must be in passed state, meaning that the approval owners must formally approve before the release passes from one stage to another.
The approvals defined by a release type can later be modified or deleted in a release using this release type.
Configure Existing Release Type
To modify existing release type click the Configure link for the corresponding type.
Delete Release Type
To delete a release type click the Delete link in the table row.
You can not delete a release type if there are existing releases of this type.
Create a Copy of Existing Release Type
Cycle allows you to easily create a complete copy of a release type , so you don't have to start defining your processes from scratch every time.
To do that simply click the Copy link in the type row
Then specify name and description for your new type and click Copy.
After clicking the Copy button you'll be redirected to the release type configuration page, where you can adjust your new release type.