| Anchor | ||||
|---|---|---|---|---|
|
| Column | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description
|
| Column | ||||||||
|---|---|---|---|---|---|---|---|---|
Table of Contents
|
Adding
UsersProjects
| Info | ||
|---|---|---|
| ||
Prior to adding a userproject, there must be an existing administrator that has been created in Zephyr Enterprise. The administrator/system user must be logged in and be under the User Project Setup section within the administration section. |
Scenario: You are a testing manager that just that has a role of a 'manager' in Zephyr Enterprise. As a testing manager, you want to add a brand new test lead as a user project in the system.
If this is your first time managing usersprojects, you might want to work with a test user project rather than an actual user project in the system, and that way, you can work out any issues you might have with managing users projects before you work with live usersprojects.
1. Click on the 
button at the top right of the interface.
2. Fill in the following mandatory fields. The mandatory fields are shown with a red bordered star next to the text and the text box border is red.
- First Name - The first name of the user.
- Last Name - The last name of the user.
- User - An individual/person who users or operates functions within Zephyr Enterprise.
- Role - A category used to give specific permissions to users in the system. These permissions give users the access and the ability to perform certain tasks throughout the system.
- Lead - Can have multiple leads per department, responsible for entire projects/releases
- Tester - Can have multiple testers per department, assigned to projects
- Dashboard - Can have multiple dashboard users. Users only have access to the dashboards of the projects they are allocated to and these users do not count towards the total license count
- Manager - Only 1 per department, essentially a manager/administrator
- Email - The email address of the user.
- Location - The location of the workplace for the user in the system.
There are plenty of optional fields such fields for the user's address, their work, mobile and home phone numbers, and fields to distinguish their business title and employee type. These fields are not necessary and are there for convenience.
- Images can be added as a resource. (JPG, GIF, and PNG that do not exceed the 2MB size limit)
| Info | ||
|---|---|---|
| ||
The default username for a new user will always be their First Name and Last Name. You have the option to select the checkbox to customize their username if you wish to do so as well. |
- 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: 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. Assign/Allocate any resources that you want to be on the new project
- Check off the users that you want to include
- Click on the green arrow to move the checked off users to the project
4. After filling in all the mandatory fields, click on the "Save" Button to create the user project in the system.