Akorbi Digital RunMyProcess makes it easy to create applications for complex business applications, such as budget application and contract management. CData Connect AI creates a live connection to Jira and can be used to generate an OData API (natively supported in RunMyProcess) for Jira. By pairing RunMyProcess with CData Connect AI, you get true cloud-to-cloud connectivity to all your SaaS and cloud-based Big Data and NoSQL sources - no need to migrate your data or write your own integrations. Simply connect to Connect AI from RunMyProcess as you would any other REST service and get instant, live access to your Jira data.
In this article, we walk through connecting to Jira from CData Connect AI and accessing Jira data through an OData feed in RunMyProcess.
About Jira Data Integration
CData simplifies access and integration of live Jira data. Our customers leverage CData connectivity to:
- Gain bi-directional access to their Jira objects like issues, projects, and workflows.
- Use SQL stored procedures to perform functional actions like changing issues status, creating custom fields, download or uploading an attachment, modifying or retrieving time tracking settings, and more.
- Authenticate securely using a variety of methods, including username and password, OAuth, personal access token, API token, Crowd or OKTA SSO, LDAP, and more.
Most users leverage CData solutions to integrate Jira data with their database or data warehouse, whether that's using CData Sync directly or relying on CData's compatibility with platforms like SSIS or Azure Data Factory. Others are looking to get analytics and reporting on live Jira data from preferred analytics tools like Tableau and Power BI.
Learn more about how customers are seamlessly connecting to their Jira data to solve business problems from our blog: Drivers in Focus: Collaboration Tools.
Getting Started
Connect to Jira from RunMyProcess
To work with live Jira data in RunMyProcess, we need to connect to Jira from Connect AI, provide user access to
the connection, and create a Workspace for the Jira data.
Connect to Jira from Connect AI
CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.
-
Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a Connection
- Select "Jira" from the Add Connection panel
👁 Selecting a data source
-
Enter the necessary authentication properties to connect to Jira.
To connect to JIRA, provide the User and Password. Additionally, provide the Url; for example, https://yoursitename.atlassian.net.
👁 Configuring a connection (Salesforce is shown)
-
Click Save & Test
-
Navigate to the Permissions tab in the Add Jira Connection page and update the User-based permissions.
👁 Updating permissions
Add a Personal Access Token
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
-
Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
-
On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a name and click Create.
👁 Creating a new PAT
-
The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
Configure Jira Endpoints for RunMyProcess
After connecting to Jira, create a workspace for your desired table(s).
-
Navigate to the Workspaces page and click Add to create a new Workspace (or select an existing workspace).
👁 The Workspaces page.
👁 Adding a new Workspace.
-
Click Add to add new assets to the Workspace.
-
Select the Jira connection (e.g. JIRA1) and click Next.
👁 Selecting an Asset (Salesforce is shown).
-
Select the table(s) you wish to work with and click Confirm.
👁 Selecting Tables (Salesforce is shown).
-
Make note of the OData Service URL for your workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}
With the connection, PAT, and Workspace configured, you are ready to connect to Jira data from RunMyProcess.
Retrieve Jira Data from RunMyProcess DigitalSuite Studio
With the connection to Jira and OData endpoints created, we are ready to add Jira data to RunMyProcess for Retrieval.
Create a Provider
- Log into RunMyProcess and open DigitalSuite Studio.
- Click Resources to bring up the Resources page, then select then the CONNECTORS tab.
👁 Connectors page
- Click the + (New Provider) button to create a new provider, choose the account to use, then click Confirm.
👁 Create a new provider
- In the provider settings page, configure the following properties.
- URL: Set the OData endpoint in the Connect AI OData page: https://cloud.cdata.com/api/odata/{workspace_name}.
- Authentication Schema: Select Login/Password.
- Login: Specify a CData Connect AI username (e.g. [email protected]).
- Password: Specify the PAT of the Connect AI user.
👁 Selecting a connector
- Fill in the same properties in the ACCEPTANCE and TEST tabs. Note: You can copy the configured settings by clicking 'Copy this configuration button,' then pasting the content in the new tab by clicking 'Paste previously copied configuration.'
- Click Save to save the properties.
Retrieve Jira Data by Creating a Connector
- In the CONNECTORS tab, click the button with three dots to create the provider, then select Add connector from the menu.
- In the following page, set Connector URL to the OData endpoint configured in Connect AI (e.g. https://cloud.cdata.com/api/odata/{workspace_name})
👁 Connector settings page
- Click Save then Launch to test the connector execution. Click Launch test to execute. The process is successful if you get the JSON response of your configured table information.
👁 Execution test page
More Information & Free Trial
Now, you have created a provider and connector to retrieve Jira data. For more information on creating OData feeds from Jira (and more than 100 other data sources), visit the Connect AI page. Sign up for a free trial and start working with live Jira data in RunMyProcess.
