# Atlassian Jira Connector Squirro provides a 1-click connector for Jira. This connector allows the Project Creators to connect to an Atlassian account and index the Jira data into Squirro. ## Set up connector Usage assumes that the OAuth setup for the 1-click connectors has already been done on the server. This is by default available on all of our cloud servers at [https://start.squirro.com](https://start.squirro.com/). For any other Squirro installation, please ask your Squirro server admin to follow the steps in the _OAuth Configuration_ section below. - Head over to the _Enterprise_ tab on the _Data_ screen as shown in the screenshot below. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2488173425.png) - Click on the _Jira_ icon. Squirro will show a prompt asking you to authenticate your Atlassian account. Click on the _Authenticate_ button there. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2488107946.png) - Once you click on the _Authenticate_ button, you will be re-directed to the Sign-in screen hosted by Atlassian. Squirro will never ask you for your Atlassian password. This is requested by Atlassian itself. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470282681.png) - Once you sign-in you will be prompted to approve Jira scopes. This screen is presented to you by Atlassian asking you to provide consent for your Jira data to Squirro. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470217015.png) - After approving scopes and selecting your Atlassian instance (if your account has access to multiple Atlassian instances), you will be brought back to Squirro’s source configuration screen. This screen shows which Atlassian account Squirro has connected to. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470217025.png) - Now, you can click _Save & Exit_ for Squirro to automatically configure the mapping of item fields and labels, as well as any other required source configuration. If your account has access to multiple Atlassian instances, Squirro will index data from the first found instance by default. The searching instance process is not deterministic and the found instance may vary across OAuth authentications. To select specific Atlassian instance provide _Atlassian instance URL_ in the _Advanced Options_ section_._ - Alternatively you can define those settings manually by clicking _Next_ and going through the whole source setup process. This allows you the full flexibility of how the Jira data should be mapped to Squirro items. - After clicking on _Save & Exit,_ you will see your source running. Sit back, relax & enjoy while we index your Jira data into Squirro. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470282787.png) ### OAuth Configuration ## App Config You will need to register an OAuth2 app on the Atlassian portal to allow Squirro to connect to the Atlassian accounts of end users. Please follow the steps below to do so. Note that the exact process on the Atlassian platform may change. If you notice big discrepancies between the current Atlassian website and the documentation page here, visit the [Squirro Support website](https://go.squirro.com/support) and submit a technical support request. - Go to **Atlassian Developer Console** here: [https://developer.atlassian.com/console/myapps/](https://developer.atlassian.com/console/myapps/), click on the _Create_ button and choose _OAuth 2.0 (3LO) integration_ option. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470282705.png) - On the next screen, choose the name of your app, accept terms and click _Create_ button. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470282711.png) - In the _Permissions_ tab add _Jira platform REST API_ service. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470184099.png) - After adding _Jira platform REST API_ service click the _Configure_ button and add the following scopes: - `View Jira issue data` - `View user profiles` [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470282811.png) - Switch to the _Authorization_ tab and configure OAuth 2.0 Authorization by clicking _Configure_ button. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470282729.png) - On the next screen configure OAuth 2 Callback URL. This is the URL Atlassian will redirect the user to after successful authorization. This needs to be set to `https:///dataloader/jira_plugin/pl/atlassian/authorized` on your server. For example: https://squirro.example-company.com/dataloader/jira_plugin/pl/atlassian/authorized. After that click Save changes button. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470217057.png) ## Apply for Production Also note that the apps are listed as a private by default. It means that only the owner of the app may grant it access to their account. The app will also show a warning about Development status during the user authorization process when the users connect their Squirro instance to their Atlassian account. To avoid that, you have to apply for publishing the Jira app. To start that process you first have to set up the logo icon and add some description about the application in the _Settings_ tab. After that follow the steps described in the _Distribution_ tab. It requires the links to the privacy policy, terms of service, customer support contact and information about how your app stores personal data. ### Squirro configuration After having created the OAuth2 app on the Atlassian portal, you need to configure the Client ID and the Client Secret on your Squirro instance. - Get the Jira Client ID and the Client Secret from the _Settings_ tab of the app. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470282741.png) This configuration will soon be possible from the user interface. - Edit `/etc/squirro/common.ini` on your Squirro cluster and add the following lines: ```python [dataloader] jira_client_id = YOUR_ID jira_client_secret = YOUR_SECRET ``` - If the `[dataloader]` header is already present in this file, add the two lines to the existing section. The section header can not appear more than once in the configuration file. - Restart the frontend & datasource service to apply the settings: ```python sudo systemctl restart sqfrontendd sudo systemctl restart sqdatasourced ``` ### Squirro Configuration After having created the OAuth2 app on the Atlassian portal, you need to configure the Client ID and the Client Secret on your Squirro instance. - Get the Confluence Client ID and the Client Secret from the _Settings_ tab of the app. [](https://s3.amazonaws.com/download.squirro.net/docs/migrated-attachments/2470216990/2470282741.png) This configuration will soon be possible from the user interface. - Edit `/etc/squirro/common.ini` on your Squirro cluster and add the following lines: ```python [dataloader] confluence_client_id = YOUR_ID confluence_client_secret = YOUR_SECRET ``` - If the `[dataloader]` header is already present in this file, add the two lines to the existing section. The section header can not appear more than once in the configuration file. - Restart the frontend & datasource service to apply the settings: ```python sudo systemctl restart sqfrontendd sudo systemctl restart sqdatasourced ``` ### Confluence / Jira GPDR Compliance Atlassian imposes rules on the handling of user personal data to be compliant with GDPR regulations for apps building on top of Atlassian products: [https://developer.atlassian.com/cloud/confluence/user-privacy-developer-guide/](https://developer.atlassian.com/cloud/confluence/user-privacy-developer-guide/) [https://developer.atlassian.com/platform/marketplace/data-privacy-guidelines/](https://developer.atlassian.com/platform/marketplace/data-privacy-guidelines/) Squirro’s 1-Click Connector does not store any personal data of any Atlassian user. It uses OAuth for Authorization. The process does not disclose any personal information, neither do we store user personal data generated / stored in an Atlassian product in Squirro. Every Squirro user has a uniqueSquirro ID. For Squirro users Squirro’s Terms & Conditions and Privacy Policy apply: [https://squirro.com/general-terms-conditions/](https://squirro.com/general-terms-conditions/)