# Frequently Asked Questions

# Is it possible to manage branched requirements in Ketryx?

Yes, there are several ways make managing branched requirements possible in Ketryx.

1. You can utilize the Change Request Item Type ( [Work Instruction-08 Change Request](https://docs.ketryx.com/work-instructions/wi-08-change-request)) to simultaneously capture intended changes to a requirement across one or multiple unreleased future versions. You may also want to consider using child requirements that capture these same intended changes and document the intended version in the _Introduced in Version_ field.

2. Alternatively, you can manage Requirements as a Git-Based item and then tag items to match the configured _release ref pattern_. ( [Manual-09 Git-based Configuration Items](https://docs.ketryx.com/manuals/man-09-git-based-configuration-items))

3. In some cases, Incremental or Scoped Releases can be utilized to enable this functionality. ( [Manual-01 Section 5.4 Versions and Releases](https://docs.ketryx.com/manuals/man-01-ketryx-lifecycle-management#id-5.4.-versions-and-releases))

4. Using item record locking can also help you point specific versions of an item at a specific release version. After doing this, you can "work ahead" on items without affecting current or upcoming releases. ( [Manual-01 Section 5.4.2 Locking item records for release baselines](https://docs.ketryx.com/manuals/man-01-ketryx-lifecycle-management#id-5.4.2.-locking-item-records-for-release-baselines))

It is additionally possible to use Jira Automation and/or plug-ins and extensions available for Jira to manage branched requirements in numerous other ways.