Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
Top
Top

Adding Projects

Info
titlePrior to Adding a Project

Prior to adding 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 add a brand new 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.

Image Removed

1. Click on the  button at the top right of the interface.

Image RemovedImage Added

2. Fill in the following mandatory fields. 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.
  • Start Date - The initial date that the project is started. This date is important as all subsequent activities and dates are set past this point.

There are optional field to fill out such as 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: Image Added

Share test cases with other projects: A project can be marked as shared which will give itits' 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

.

Image Removed

3. Assign/Allocate any resources Select the projects that you want to be on the new projectshare test cases with.

  1. Check off the users project(s) that you want to includeshare test cases with.
  2. Click on the green arrow to move the checked off users project(s) to the projectselected shared projects

4. After filling in all the mandatory fields, click on the "SaveAdd" Button to create the project in the system. 


Back to Top ^