---
title: "How does Ketryx enable users to work on multiple versions and deployments for the same project?"
description: "Multiple versions of the same project may exist at one time and exist in varying states. See MAN-01 Ketryx Lifecycle Management for creating and associating versions. Each configuration item for a project has an \"Introduced in version\" field."
category: "Frequently Asked Questions"
section: "Software Release Process"
keywords: ["deployments", "multiple versions", "exist", "users", "enable", "work", "introduced version", "effective"]
source_url: "https://support.ketryx.com/hc/en-us/articles/25923740034701-How-does-Ketryx-enable-users-to-work-on-multiple-versions-and-deployments-for-the-same-project"
last_reviewed: 2026-06-11
---

# How does Ketryx enable users to work on multiple versions and deployments for the same project?

> **In short:** Multiple versions of the same project may exist at one time and exist in varying states. See MAN-01 Ketryx Lifecycle Management for creating and associating versions. Each configuration item for a project has an "Introduced in version" field.

Multiple versions of the same project may exist at one time and exist in varying states. See [MAN-01 Ketryx Lifecycle Management](https://docs.ketryx.com/manuals/man-01-ketryx-lifecycle-management#id-6.4.3.-step-3.-create-and-associate-versions) for creating and associating versions.

Each configuration item for a project has an "Introduced in version" field. This field ties that item specifically to the version they are effective in. Additionally, you may designate an "Obsolete in version" field which indicates that the item is no longer effective from that version onwards.

See this [FAQ](https://support.ketryx.com/knowledge/editor/01HM74V01RWQRZ9CMKQYG2BZK0/en-us?brand_id=21249112595853) on the difference between long-lived and point-wise items.

Using the "Introduced in version" field, and creating multiple project versions, users can work on features and configuration items across multiple deployments. As a result, each version may exist in different phases of the software development life cycle, allowing your teams to work efficiently, while also maintaining compliance and traceability.

## Related articles

- [What are long-lived and point-wise (short-lived) configuration items? What are the differences between the two?](what-are-long-lived-and-point-wise-short-lived-configuration-items-what-are-the.md)
- [Is the release version in Jira the same as the one in Ketryx?](is-the-release-version-in-jira-the-same-as-the-one-in-ketryx.md)
- [When are Change Requests, CAPAs, Anomalies, and Complaints included in the Change Management File](when-are-change-requests-capas-anomalies-and-complaints-included-in-the-change.md)
- [What is the difference between a Software Item Spec and a Task in Ketryx?](what-is-the-difference-between-a-software-item-spec-and-a-task-in-ketryx.md)
- [How do I exclude items with an 'obsolete' status from Ketryx?](how-do-i-exclude-items-with-an-obsolete-status-from-ketryx.md)