> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/requirements/clone-multiple-requirements.md).
# Clone Multiple Requirements
Reuse one or many requirements in your next effort(s) by cloning requirements. Cloned requirements will start at version 1 and can be independently modified in the destination program(s); changes are not synchronized across programs. Comment history is removed for a fresh start.
To clone an entire program and all of its contained requirements and systems, see [Clone Programs](/features/programs/clone-programs.md)
### Select Requirements to Clone
From the originating program tabular view, use the checkboxes to select one or more requirements (including nested requirements) and/or folders. Right click on the highlighted rows and select **Clone to Program.**
Use the dialog to select the destination program:
### Configure the Clone
In the dialog, select the cloning options to achieve the desired state in the destination program.
* **Preserve Hierarchy:** retain any nesting of the selected requirements. If you skip a nesting level, the child requirements will move up one nesting level
* **Keep original folder structure**: retain any folders and their contained requirements. If not selected, requirements in a folder will be bumped up a level in the hierarchy
* **Group everything into a new folder**: place cloned requirements and folders in a new folder for reference when deciding where to move/incorporate the newly-cloned requirements (you can delete the folder afterwards). If you don't provide a folder name, a default "Cloned from \[Program] - \[Timestamp]" name will be provided. If not selected, cloned requirements are appended to the bottom of the list in the destination program.
* **Relationships:** Retain existing relationships to other Violet entities in the cloning process.
* **Verifications and Evidence:** Clone verifications and any associated evidence
The following configuration options permit a variety of mapping and cloning actions:
* **Systems**
* **Custom Requirement Attributes**
* **Custom Verification Attributes**
Each offers the following actions for each system or attribute:
1. Map to..(systems only): select the desired destination system to convert the source item
2. Create in destination (systems or attributes): add the system or attribute to the destination program, and copy in the attribute values
3. Clear values (attributes only): add the attribute to the destination program, but clear any populated values
4. Don't clone: don't include the system or attribute in the destination program
Optionally, enter a name for this configuration if you'd like to apply it again in a future cloning process from the same originating program (note: some adjustments to mappings may be required if destination program attributes and systems differ from those in the original destination).
Click Clone.
### Organizing Cloned Requirements
Newly cloned requirements are found at the bottom of the list in table view, or in a folder if that option was selected in the configuration process.
Use Violet's Requirement Organization features (see [Getting started](/features/requirements/getting-started.md)) to drag and drop the new requirements into their appropriate location in your program.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.violetlabs.com/features/requirements/clone-multiple-requirements.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
