Project settings (in the Projects module)
- General settings
- Project roles
- Ticketing system
- Settings Issue workflow
- Archive / Delete
- Marker settings
- Activity settings
To assign a project to a user, you must go to the project role submodule. All other users (who don’t have roles in the project) don’t have permission to work with the project. If other users see the project, they can’t see the details or other sub-modules (only for users with the “super admin” role). Roles are described in the “Roles” module, where you can change or add new ones as needed (see the “Roles” module for more information).
A ticketing system is an issue reporting system. You can synchronise JunoOne with another system for issue management. You can choose from 4 options:
For JIRA and OTRS, you need important login and synchronisation information. More information can be found at system documentation.
n this submodule you can choose from four export areas:
- Test Plan
- Test Analysis
- Test Execution
You can customise the export as needed. Selecting specific information and checking selected fields will filter the table.
Setting Issue workflow
This submodule is one of the most important settings. The user has permission to work with the project, but can’t change the issue status (click here for more information on issues). Here you can create your own Issue workflow, where you set the user permission to change the status from current to planned.
You can also export the Issue workflow to a .xlsx document and import it into another project.
Template for issue workflow
To import the issue workflow into a project, you must use a .xlsx document (download template here). If a status with the same role already exists, new data won’t be added.
Archiving & Deleting a Project
Another function is archiving the project. If a project is stopped or completed, you can archive it and use it in the future if necessary. When a project is archived, it can’t be opened or edited, but can be unarchived.
The deletion loses all data in the project permanently (test cases, test plans, issue workflow…).
Tagging is one of the other options for setting-up a project. In this section, you can create tags that are further used in test execution, test analysis, and issue handling. The “waiting for retest” tag is set as the default tag in each project and is used to indicate which tests can be retested (it is bound to a test that has been assigned an issue and the issue has been closed – it has a closed status).
Use in other modules: