Skip to main content

← Back to parent Epic

MAZENG-FT-14 · Retire a project

Feature intent

An owner needs to remove an obsolete project from active work without presenting it as current.

Why it matters

An owner needs to remove an obsolete project from active work without presenting it as current.

Expected outcome

Keeps project lists relevant while supporting a controlled retention policy.

In scope

  • Require confirmation that identifies the project to be retired.
  • Archive the selected project rather than ambiguously claiming immediate permanent deletion.
  • Remove the retired project from active project lists and return the user to a safe location.
Delivery status
IN_BACKLOG
Owner
RootAtSkic (product lead)
Parent Epic
MAZENG-EP-3
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    Only an authorized project role can retire the project.

  2. 02

    Confirmation clearly identifies the affected project.

  3. 03

    After successful retirement, the project no longer appears in active lists and navigation returns to a safe page.

  4. 04

    An unauthorized or failed attempt leaves the project active and unchanged.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Legacy labels the action as deletion while implementing soft archival; Next Gen terminology must preserve the actual user outcome.
  • Retention duration, restoration, dependent-resource treatment, and permanent-deletion semantics require explicit product decisions.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source