Create & Manage Projects
Projects are the main entity in your application, providing key benefits such as granular user access control for test cases via roles and permissions. They help maintain separation of concerns by grouping each project's test cases, test runs, defects, and requirements under one framework, enhancing both focus and productivity.
When creating a project, you will need to provide the following details:
- Name
- Description
- Photo
- Is Completed (to track the status of completed projects)
- Is Public (if public, the project is accessible to everyone in the organization)
The Is Public field offers better control over user access. Here's how access works depending on the field value:
| Is Public | Role |
|---|---|
| Yes | The project is accessible to everyone in the organization. However, you must select a global role that defines what actions users can perform in the project. |
| No | The project is restricted, and you must manually assign access to specific users or groups through the appropriate tabs. |
If you choose not to make the project public, you will need to manually add users or groups. For each, you can assign a unique role, giving you more control over permissions.
Note : If you assign a role to a group but need to adjust permissions for individual users within that group, you can add them separately with their own role. The role assigned at the user level will override the group-level role.
Note : Users with owner/admin access levels have full access to all projects and can perform any action.
Starred Projects
You can mark projects as starred for quick access on home page.