New Features
Release Activity Dependency
Now, you can add dependencies between Activities/Criteria within a Release. The Activity/Criterion window has a new section ‘Dependency’. Click 
on this window to add dependencies between the Activities/Criteria. Refer to the Manage Release Activities article for details.
This feature ensures that the Activities/Criteria are completed in the correct order. Plutora restricts you from setting the status of an Activity/Criterion ‘In Progress’ or ‘Completed’ unless all the preceding Activities/Criteria are resolved (i.e have a status Completed or N/A).
In case of unresolved dependencies, the options ‘In Progress’ and ‘Completed’ in the Status drop-down will be disabled.
You can track the addition and removal of dependencies in the Audit.
Bulk Update Activities/Criteria Status
During Bulk Update, if the selected Activities/Criteria have a dependency and the dependent Activities/Criteria are not included as part of the Bulk Update, then on selecting 
, Plutora will display a notification to confirm your actions with the details about the dependent Activities/Criteria.
In this case, the status of the Activities/Criteria with resolved dependency (or no dependency) will be updated, and the status update of those with unresolved dependency will be aborted.
Update Activity/Criterion Due Date
Updating the Due Date of an individual Activity/Criterion to a future date will give you an opportunity to shift the Start Date, Due Date, and Forecast Date of all the successor Activities/Criteria that depend on this Activity/Criterion. In this case, a pop-up will display the list of all the successor Activities/Criteria.
It also applies to the Shift Dates option in the ‘Bulk Update Activities’ window.
Manage Portfolio Association for SSO Users
Now, you can set the user Portfolio Associations via SSO. See example. This enhancement enables you to assign the users to a Portfolio Association with limited access to Plutora modules.
Either of the following Name values can be used (case insensitive):
- Organization
- Organisation
- PortfolioAssociation
- Portfolio Association
- Portfolio
If the Portfolio Association attribute in the SAML response is left empty or if the Portfolio Association listed in the SAML response does not match any existing Portfolio Association in Plutora, Plutora will assign the top-level Portfolio Association to the new users but will not make any updates to existing users so this can be managed within Plutora’s user management.
Bug Fixes
- 24325: [API] /DeploymentPlan/Update/{ID} You can now update to downstream portfolio association.
- 24341: [Deployment Plan] Now, to save Deployment Plan you must fill the mandatory custom fields.
Version Number
2.29.0
Regional Release Schedule
*Subject to change.