Bug management and tracking issues are essential components in the software release process. It is important to resolve all issues to deliver quality software. CloudBees Release Orchestration SaaS can give your team a single view of all bugs and issues related to the deployment of a new feature.
In CloudBees Release Orchestration SaaS, you can configure your bug management tool to find, track, assign, and close software bugs and issues.
Configuring bug management
To configure bug management:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select Bug management on the left pane.
-
Enter a Tool Name.
-
Select a Tool Type from the options.
-
Enter the Tool URL.
-
Enter the API Token to access the tool in the specified format.
-
Enter the User Name.
-
Select from the options to file a bug.
Figure 1. Bug management configuration -
Select SAVE.
Your bug management configuration is saved and listed on the right pane.
Updating a configuration
You can update the bug management configuration.
| Select RESET to clear your selection at any time. |
To update your bug management configuration:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select Bug Management on the left pane.
-
Select a configuration on the right pane.
-
Make any updates.
-
Select Update.
Your bug management configuration is updated.
Deleting a configuration
To delete your bug management configuration:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select Bug Management on the left pane.
-
Select a configuration on the right pane.
-
Select
Delete. -
Select DELETE.
Your bug management configuration is deleted.
| You can only update mapping configurations that are not Pending. |
Mapping a project to bug management
You can assign a project to the bug management tool.
To assign a project to bug management:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select Bug management on the left pane.
-
Select a Pending project from the right pane.
-
Select Configure Mapping.
-
Map your custom fields to any of the tool fields:
-
Bug Title: bug title.
-
Bug Assignee: name of the user who has filed the bug.
-
Bug Reporter: name of the user who is reporting the bug.
-
Bug Priority: priority level of the RIQ bug.
-
-
Map your bugs to any project stage and epic in Jira (or component, for Classic Jira):
-
Build Issues: a Jira epic for the build stage.
-
Deploy Issues: a Jira epic for the deploy stage.
-
Test Issues: a Jira epic for the test stage.
-
Other Issues: a Jira epic for a custom stage.
Figure 2. Mapping bugs to Jira project management -
| Each project must have only one mapping. If you use Classic Jira as your bug management tool, you must map your bugs to components, not epics. |
Your project is assigned to bug management.
| You can select RESET to clear your selection at any time. |