OverOps integrates with Atlassian's Jira tool to allow opening and managing issues directly from the OverOps web application, and enhancing efficiency by incorporating OverOps into existing ecosystems.
To connect OverOps to your Jira account:
- From the OverOps Dashboard, click Settings and select Jira.
The Jira Settings dialog box opens.
- Turn Jira On.
- Enter Jira host and your Jira credentials, and then click Save.
OverOps saves these details.
Once you’ve setup the integration, Jira issues can be opened for specific, or a group of exceptions.
There are a number ways to open Jira issues from OverOps.
To open Jira issues from OverOps:
- From the Dashboard, right-click the event and select Send to Jira:
Hover over the event for the Event toolbar. From the Event toolbar, click for more options, and select Send to Jira:
Click on the event and from the Error Analysis page, click Send to Jira:
The event details window opens:
OverOps provides a default title and description of the event.
- Select the project to which to add the issue and set the issue type.
- Edit event summary and description if necessary.
- Fill in the Due Date and click Create Jira Issue.
A Jira issue is created and linked to the event in OverOps:
- Click the link to open the issue in Jira:
Once an Issue is opened in Jira, the event is marked with a Jira label.
To view the Jira issue in OverOps:
- From the Event, click and select View Jira Issue:
The Jira Issue dialog box opens displaying the mandatory fields set for the Jira project:
Note: For admin users only.
Disabling Access to Jira projects from OverOps
OverOps enables admin users to disable access to certain projects.
To disable access to Jira projects from OverOps:
- From the Dashboard, click Settings and from the list, select Jira.
The Jira Settings dialog box opens:
- From Available Projects, click Load Projects.
- From the drop-down list, uncheck the Jira projects to which to disable access from OverOps and click Apply. By default, all projects are available to send issues to.
By default, OverOps searches for the Jira host via the OverOps cloud, but if the On-premises Jira environment cannot be accessed, OverOps tries to connect through a "local" OverOps Collector. This may cause delays impacting the user experience.
To make the communication to the On-Premises Jira environment more stable, it is recommended to provide the internal On-Premises Jira environment domain name and set the Self-hosted Jira flag as the Jira hostname. This forces OverOps to connect to the On-Premises environment from the Collector(s) only and stay within the private network as long as the internal Jira domain name is routed accordingly.
To set communication through Collectors only:
- From the Jira Settings dialog box, click View advanced settings:
- From Deployment Settings, select Self-hosted Jira.
The Self-hosted JIRA flag enables the communication to your JIRA environment from the Collector(s) only.
Set Global Jira Credentials
OverOps enables admin users to set global credentials for all its members.
To set global Jira credentials:
- From the Jira Settings dialog box, check the Use same Jira credentials for all teammates checkbox.
To retrieve the global Jira credentials from the properties file located on the Collector machine:
- Check the Read credentials from the collector's properties file check box.
- To connect via the Collector to the Jira on-premises, from Deployment Settings, select Self-hosted Jira.
- From the Collector, open the collector.properties file:
From Linux: /opt/takipi/collector.properties
From Windows: c:\takipi\collector.properties
From MacOS: /Library/Takipi/collector.properties
- Add the following parameters at the end of the file:
OverOps allows you to create Jira issues automatically, with View-based rules (as in Alerts feature).
- From the Alerts Settings dialog box, select Default Settings and click the Jira tab.
- Click Configure and set the Jira issue parameters:
- When finished click Save Settings.
- Select View Settings and choose the Views and conditions for which to create Jira issues.
- When finished, click Save Changes.
Events will now be sent to Jira for the configured Views automatically.