26.2 enhancements and patches
26.2
Assess the impact of change requests automatically
Administrators can define rules to automatically analyze the impact of change requests at configured change lifecycle events, such as change creation or status transitions. When impact analysis runs, the system automatically relates the relevant configuration items (CIs) based on the rule conditions and association options. This approach standardizes CI associations for change requests and reduces manual effort during change processing.
For more information, see Configuring the impact analysis settings.
What else changed in this release
The following table lists the changes in the product behavior:
Update | Product behavior in versions earlier than 26.2 | Product behavior in version 26.2 |
|---|---|---|
Change request approval behavior during Impact Analysis
| Change requests could be submitted for approval or moved to another status while an Impact Analysis run or post‑run activities were in progress. | Change requests cannot be submitted for approval or moved to another status while an Impact Analysis run or related post‑run activities are in progress. Status transitions are blocked until the Impact Analysis run and all post‑run activities are complete. For details, see Performing an impact analysis for a change request.
|
| Post‑impact analysis CI association handling for incidents | After impact analysis, existing CI relationships were always retained. | Post‑impact analysis association for incidents includes association options. Administrators can choose to add impacted CIs to existing associations or delete existing Impact relationships and create new ones. For more information, see Configuring the impact analysis settings. |