---
title: "Can an item retain its approvals when transitioning from a controlled status (e.g., Closed/Approved) to 'Obsolete'?"
description: "To maintain approvals when transitioning from a controlled state such as \"Approved\" or \"Closed\" to an obsolete or removal state in Ketryx, begin by adding an \"Obsolete\" status (or any name you choose) to your Jira workflow."
category: "Frequently Asked Questions"
section: "Advanced Settings"
keywords: ["transitioning", "closed approved", "obsolete", "controlled status", "retain", "approvals", "state", "removal"]
source_url: "https://support.ketryx.com/hc/en-us/articles/38205586792973-Can-an-item-retain-its-approvals-when-transitioning-from-a-controlled-status-e-g-Closed-Approved-to-Obsolete"
last_reviewed: 2026-06-11
---

# Can an item retain its approvals when transitioning from a controlled status (e.g., Closed/Approved) to 'Obsolete'?

> **In short:** To maintain approvals when transitioning from a controlled state such as "Approved" or "Closed" to an obsolete or removal state in Ketryx, begin by adding an "Obsolete" status (or any name you choose) to your Jira workflow.

To maintain approvals when transitioning from a controlled state such as "Approved" or "Closed" to an obsolete or removal state in Ketryx, begin by adding an "Obsolete" status (or any name you choose) to your Jira workflow. Ensure this status is included in the [removalStatusNames setting](https://docs.ketryx.com/reference/advanced-settings#removal-status-names) under Project Advanced Settings so Ketryx recognizes it as a valid removal endpoint. Next, in the [Approval Workflow Configuration section](https://docs.ketryx.com/reference/advanced-settings#approval-workflow) of the advanced settings, identify the item type (such as Requirement or Test Case) and set the relevant controlled states. For the controlled state you’re transitioning from (e.g., "Approved"), set "isControlled" to true and specify the obsolete state in the "keepApprovalsWhenTransitionedTo" list. Also, for the obsolete state itself, set "isControlled" to true. This setup ensures that transitioning to the obsolete state retains the original approvals and maintains traceability, allowing you to safely retire controlled items without compromising compliance. See below for a visual example of how the approval workflow can be configured in the advanced settings.

## Related articles

- [How do I exclude items with an 'obsolete' status from Ketryx?](how-do-i-exclude-items-with-an-obsolete-status-from-ketryx.md)
- [Why is my item unexpectedly being moved back to Resolved after being approved?](why-is-my-item-unexpectedly-being-moved-back-to-resolved-after-being-approved.md)
- [Can Ketryx invalidate items that use custom workflows?](can-ketryx-invalidate-items-that-use-custom-workflows.md)
- [How do I ensure my Test Cases are controlled before I create Test Executions?](how-do-i-ensure-my-test-cases-are-controlled-before-i-create-test-executions.md)
- [What Advanced Settings should I change when I \"Use existing Jira configuration\" for a new Ketryx Project](what-advanced-settings-should-i-change-when-i-use-existing-jira-configuration.md)