Skip to main content
Version: 1.2.1

Version 1.1.1

Improvements​

Release life cycle

An expanded state model allows the product owners and users responsible for the release to manage the release cycle more efficiently. For this purpose, we have added new states: Planning (defining the pool of tasks to be released), In progress (work on a release – building and publishing) and Canceled. New state transitions have been configured for these states.

Cancel release

You can now cancel an unpublished release. When a release is canceled, a modal window appears that displays the number of incomplete tasks, if any.

One of three actions can be selected for the incomplete tasks:

  • Cancel
  • Remove from the release
  • Move to a different release (you can select a release in the Planning, Planned or In progress state)

Moving to archive

Published releases that are no longer relevant can be archived. Previously this action was available for the releases in any state. All fields of the release form in the Archive state, except for the Work notes, are read-only.

The Move to archive modal window has been updated.

Updated field behavior

Only a release in the Planning, Planned or In progress state that is related to the product selected for the task or a sprint project can be selected in the Release field on the SDLC task and sprint forms.

Only a release in the Released or Archive state that is related to the product specified in a defect can be selected in the Detected in release field on the defect form.

Fixes​

DEF0018391: A user with the pda_admin role was unable to use some features available to the users with the pda_user role. For example, they could not be added as a project member. In the new version, the pda_admin role inherits the pda_user role and the role model works as intended.

DEF0018331: Access control rules for the Product Module table have been corrected, so the product owners can edit the modules of their products even if they do not have the pda_admin role or are not the module owner.

DEF0018275: The reference qualifier settings for the Project field of the Project Member table have been corrected. This has fixed the error that prevented creating a new project member.