Methodology pack upgrade

Move the project to a newer version of the methodology pack. See what changes before you confirm.

This page applies to the System and project configuration stage.

Page in the app: /admin/methodology, /p/{projectId}/settings/pack-upgrade

Safe upgrade

Upgrades only go forward. Plan them between gates.

  1. Compare. See new phases, fields and rules.
  2. Check the effect. The app lists items that need attention.
  3. Confirm. A person with the right role confirms.
  4. Applied. The change is logged.

Project manager guide

Move the project to a newer pack version without surprises.

  1. Choose a version and check.
    • Do now: Pick the target version and select Check.
    • Why: You see the effect before anything changes.
    • The app checks: The check lists items and settings that fail the new version, and the open approvals it affects.
    • Next: Fix or map what fails.
  2. Map the states.
    • Do now: Where a state no longer exists, choose the state its items move to. Check again after every change.
    • Why: Items in a removed state would otherwise be stuck.
    • The app checks: The upgrade is refused while an item or a setting still fails. A changed mapping needs a new check.
    • Next: Apply the upgrade.
  3. Apply between gates.
    • Do now: Select Apply upgrade and confirm.
    • Why: It cannot be undone, so pick a quiet moment between gates.
    • The app checks: The upgrade is refused when the project changed after the check. The result is logged with a correlation ID.
    • Next: Look at the audit log if you need proof.

How to do it

  1. Read the differences. Look at each change.
  2. Confirm. Run the upgrade when the team is ready.

Related topics

Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.

Last updated: