Archive a landscape

Archiving retires a landscape that is no longer used. A landscape linked to tickets, transports or releases can’t be deleted (see Landscapes configuration), so archiving takes it out of use instead and keeps its complete history for audit purposes.

Requirements:

  1. The user has the IRTAdmin or IRTLandscapeManager role (see User management).

  2. An individual landscape that is part of a composite landscape can’t be archived on its own. Archive the composite landscape instead - it archives all its landscapes.

1. What archiving does

  • All active tickets of the landscape (In development and In transport) are canceled together with their transports and releases.

  • The landscape becomes unavailable for transports and other DevOps operations. Its tickets, transports and their history stay readable.

  • The archive date is recorded and shown on the landscape page.

Archiving is irreversible. An archived landscape can’t be restored, so create a new landscape if the systems are needed again.

2. Archive a landscape

To archive a landscape follow steps:

  1. Go to Config → Landscapes page.

  2. For a composite landscape select Composite in the Landscapes Type selector.

  3. Open the landscape clicking on its edit button.

  4. Click on Archive button. It opens the Confirm Archive dialog:

    Click 'OK' to archive the landscape. This action will cancel all active tickets, transports, and releases. Additionally, the landscape will become unavailable for transport and general use while preserving its complete history for audit purposes.

    If the landscape has active tickets, the dialog also lists the technical ticket ids that will be canceled.

  5. Click on OK.

3. After archiving

  • The landscape page shows the warning Landscape <name> was archived on <date> and its settings can’t be changed anymore.

  • The Landscapes page hides archived landscapes. Switch on Show archived landscapes to see them.

  • Archived landscapes aren’t offered wherever a landscape is picked: Landscape Overview (including the Landscape Overview actions on Tickets, Object Info and B2B Scenarios), Migration to IS, the Home page landscape block and the landscape selection of the Change Log (Show versions across landscape).

  • Any DevOps operation on a ticket or transport of an archived landscape is rejected with the error Operation '<operation>' cannot be performed because the associated object relates to archived landscape '<name>'. Operations to archived landscapes are not allowed.