Editing a Project

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

Editing Projects

Prior to Editing a Project

Prior to editing a project, there must be an existing administrator that has been created in Zephyr. The administrator/system user must be logged in and be under the Project Setup section within the administration section.

Scenario: You are a testing manager that has a role of a 'manager' in Zephyr. As a testing manager, you want to edit an existing project in the system.

If this is your first time managing projects, you might want to work with 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 projects before you work with live projects.


1. Click on the individual project that you want to edit.


2. Change/Edit any the existing fields for the project. The project must have the mandatory fields filled out. The mandatory fields are shown with a red star next to the text and the text box border is red.

  • Name - The unique name given to a project to distinguish a project. This date is important as all subsequent activities and dates are set past this point.
  • Start Date - The initial date that the project is started

There are optional fields to fill out such as a description for the project, selecting an end date, mapping the project to an external defect project from JIRA, selecting a lead to be on the project as well as an option to change the project type.

There are a total of 3 different project types.

  • Normal (N) Projects - Default project type. Users assigned to a normal project are able to view the testing assets of all other normal projects including the Global Trees of the test repository and test execution. Users that are only assigned to a normal project cannot view the testing assets of restricted and isolated projects.

  • Restricted (R) Projects - Users assigned to a restricted project are not able to view the testing assets of isolated projects but can see those assets in a normal project. Restricted projects are typically useful for restricting access to sensitive data that only members of the project can see.

  • Isolated (I) Projects - Users assigned to an isolated project are not able to view the testing assets of any projects nor can anybody see the testing assets of their project. Isolated projects are typically useful to completely isolate a project and its testing assets. For example, it might be ideal to whenever you want to host multiple customer projects on the same instance of Zephyr.

Shared: A project can be marked as shared which will give it's test resources the ability to be copied to other projects marked as shared. Project sharing is restricted to projects with type "Normal".

  • Project sharing can not be disabled after test case sharing is started.

3. Allocate/Deallocate any resources for the existing project

  1. Check off the users that you want to include/exclude
  2. Click on the green arrow to move the checked off users to and from the project

4. After making the final edits/changes, click on the "Save" Button to finalize the changes for the project in the system. 


Back to Top ^