![]() Separate projects are added for different teams. Situation: On ReportPortal instance there are several projects. If the integration requires some changes, the Administrator can easily edit an integration, and the changes will apply to all projects on the instance. Pros: Administrator configures integration once, and should not perform the same action several times. Solution: configure global integration for Jira (or Rally) plugin on the Management board. Different projects post new bugs in the same Jira (or Rally) project. The team works with one project in Jira (or Rally). Separate projects are added for different test types (UI, API, Unit and other). Situation: A small team, on ReportPortal instance there are several projects. If the user configures a plugin on the project level, then these configurations will be applied to only this project and replace global configurations, in case they are.ĭetails on how to configure a specific plugin please find in the Integration section: ![]() If a user configures plugin on the global level, then these configurations will be applied to all projects on the instance, which do not have their own configurations. The configuration is the same for both levels. Users can configure a plugin on the instance-level (global configuration) and also on the project level (project configuration). Only ADMINISTRATOR can make global configurations of a plugin.ĪDMINISTRATOR and PROJECT MANAGER can make project configurations of a plugin. All plugin configurations will be deleted from the DataBase. The plugin will be successfully deleted. ![]() Users can remove a plugin from the system. Only ADMINISTRATOR can uninstall the plugin. But all plugin configurations will be saved in the DataBase and you can return them back if you need by clicking on the switcher enable the plugin. The plugin will be removed from Project Settings on the project spaces.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |