Deallocating and Allocating a Requirement

Owned by Kevin Pham (Deactivated)
Last updated: Jun 13, 2018

Steps to Deallocate and Allocate Requirements

The following sections will need to be followed to deallocate and allocate:

Deallocating Requirements

Prior to Deallocating a Requirement

Prior to deallocating a requirement, there must be an existing project, release, and requirement that has been created in Zephyr. The project/release must be selected and the user must be under the Requirements section within the release selected. 

Scenario: You are a testing manager in Zephyr. As a testing manager, you want to deallocate an existing requirement that you don't want to fully delete but want to remove from the current release. You might possibly need the requirement later down the road and we'll go into detail with allocating requirements further down. The requirement will be deallocated in the release.

If this is your first time managing requirements, you might want to work within a test project rather than an actual project in the system, and that way, you can work out any issues you might have with managing requirements before you work with live requirements.


1. Select/check off any of the requirements that you want to deallocate on the left hand side of the table.

2. Once you have your selected requirement(s) to deallocate, you simply click the "Delete" button at the top of the table.

Note

The ability/feature to deallocate a requirement is located within the "Delete" button. So as a user, you need to click on the "Delete" button to have the option to deallocate.

3. There will be a pop-up that gives you two options:

  • Deallocate - This removes the requirement from the current release but keeps the requirement within the Global Tree/Folder. You can still retrieve and use this requirement if you want to by utilizing the Global Tree/Folder.
  • Delete - This removes the requirement in its' entirety and you cannot get the requirement back.
    • Please refer to the Delete page for additional information on these steps.

4. Simply click on the "Deallocate" button and the requirement will be removed from the current release and can be found in the Global Tree/Folder.


5. You can find and view the recently deallocated requirement in the Global Tree/Folder.


Back to Top ^

Allocating Requirements

Prior to Allocating a Requirement

Prior to allocating a requirement, there must be an existing project, release, and requirement that has been created in Zephyr. The project/release must be selected and the user must be under the Requirements section within the release selected. The requirement must have already been deallocated and must be located in the Global Tree.

Scenario: You are a testing manager in Zephyr. As a testing manager, you want to allocate an existing requirement that was deallocated from the current release. We'll be using deallocated requirement from the previous steps located above. The requirement will be allocated in the release.

If this is your first time managing requirements, you might want to work within a test project rather than an actual project in the system, and that way, you can work out any issues you might have with managing requirements before you work with live requirements.


1. Select/check off any of the requirements that you want to allocate on the left hand side of the table within the Global Tree.

2. Once you have your selected requirement(s) to allocate, you simply click the "Allocate" button at the top of the table.

  • The requirements selected will be allocated to the release that it was originally deallocated from. It will be moved back to the current release but will also remain in the Global Tree.

3. You can find and view the recently allocated requirement in the release/folder that the requirement belongs to.


Back to Top ^