Atlassian Jira
Last updated
Last updated
Open-source and On-premise editions of Ylem require separate specific configurations for this integration. See below
Integration type: Write
Integration with Atlassian Jira allows you to create tickets there in real time based on the streaming events you define in Ylem pipelines.
Data for the connection:
If you don't use the cloud version of Ylem but have it installed on your infrastructure under your domain name, you can choose one of the following two ways how to make this integration work.
It is the same way how it works in our cloud version. You need to create your own Atlassian Application and integrate your Ylem instance with it so that your users will be able to authorize Ylem to access their Atlassian accounts.
As the first step, you need to go to the Developer Console of Atlassian and create your own "OAuth 2.0" application.
These are the data and the scopes required for this application to work with Ylem:
As soon as the application is ready, you can open its "Settings" and copy your CLIENT_ID and CLIENT_SECRET. These two values you will need to add to your Ylem configuration now.
The following parameters need to be changed on the backend/integrations/.env
file:
Now you can open https://%%YOUR_YLEM_DOMAIN_NAME%%/jira-authorizations and try to authorize Jira Integration by clicking on the button "Add Jira authorization".
Another way of creating an integration with Atlassian Jira to be able to create issues directly from Ylem is using its REST API with Personal Access Tokens (PAT).
Personal Access Token (PAT) is a safe alternative to using username and password for authentication with various 3rd-party services like Ylem.
This page contains a detailed explanation of how it can be created:
As soon as you have your PAT configured, you can use it as an Access Token for POST/GET requests to Atlassian API.
Check Atlassian REST API reference and create a Ylem API Integration with it:
Now you can call it directly from the Ylem pipelines with the necessary query parameters and headers using the API_Call task.