Ylem documentation
  • 🗒️General information
    • Introduction to Ylem
    • Quick start guide
    • Release notes
  • 🔬Open-source edition
    • Installation
    • Usage of Apache Kafka
    • Task processing architecture
    • Configuring integrations with .env variables
  • 💡Integrations
    • Connecting an integration
    • Library of integrations
      • Amazon Redshift
      • Apache Kafka
      • APIs
      • Atlassian Jira
      • AWS Lambda
      • AWS RDS
      • AWS S3
      • ClickHouse
      • ElasticSearch
      • E-mail
      • Google Big Query
      • Google Cloud SQL
      • Google Pub/Sub
      • Google Sheets
      • Immuta
      • Incident.io
      • Jenkins
      • Hubspot
      • Microsoft Azure SQL
      • MySQL
      • OpenAI ChatGPT
      • Opsgenie
      • PostgreSQL
      • PlanetScale
      • RabbitMQ
      • Salesforce
      • Slack
      • Snowflake
      • Tableau
      • Twilio. SMS
      • WhatsApp (through Twilio)
    • Initial demo data source
  • 🚡Pipelines
    • Pipeline management
    • Tasks
      • Aggregator
      • API Call
      • Code
      • Condition
      • External trigger
      • Filter
      • For each
      • GPT
      • Merge
      • Notification
      • Query
      • Pipeline runner
      • Processor
      • Transformer
    • Running and scheduling pipelines
    • Library of templates
    • Environment variables
    • Mathematical functions and operations
    • Formatting of messages
  • 📈Statistics and profiling
    • Statistics of runs
    • Slow tasks
  • 📊Metrics
    • Metric management
    • Using previous values of a metric
  • 💼Use cases, patterns, templates, examples
    • Use cases
    • Messaging patterns
      • Datatype Channel
      • Message Dispatcher
      • Messaging Bridge
      • Message Bus
      • Message Filter
      • Message Router
      • Point-to-Point Channel
      • Publish-Subscribe Channel
      • Pull-Push
    • Functional use cases
      • Streaming from Apache Kafka and messaging queues
      • Streaming from APIs
      • Streaming from databases
      • Data orchestration, transformation and processing
      • Usage of Python and Pandas
      • KPI Monitoring
      • OKRs and custom metrics
      • Data Issues & Incidents
      • Reporting
      • Other functional use cases
    • Industry-specific use cases
      • Finance and Payments
      • E-commerce & Logistics
      • Customer Success
      • Security, Risk, and Anti-Fraud
      • Anti-Money Laundering (AML)
  • 🔌API
    • OAuth clients
    • API Reference
  • 👁️‍🗨️Other resources
    • FAQ
    • Our blog on Medium
Powered by GitBook
On this page
  • Configuring integration for open-source and on-premise versions
  • Using Atlassian Application and OAuth 2.0
  • Using API integration, Atlassian API, and PAT

Was this helpful?

Edit on GitHub
  1. Integrations
  2. Library of integrations

Atlassian Jira

PreviousAPIsNextAWS Lambda

Last updated 7 months ago

Was this helpful?

Open-source and On-premise editions of Ylem require separate specific configurations for this integration. See

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:

Configuring integration for open-source and on-premise versions

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.

Using Atlassian Application and OAuth 2.0

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.

Step 1. Create Atlassian 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.

Step 2. Configure Ylem .env parameters

The following parameters need to be changed on the backend/integrations/.env file:

INTEGRATIONS_JIRA_OAUTH_CLIENT_ID=%%REPLACE_IT_WITH_THE_CLIENT_ID_OF_YOUR_APP%%
INTEGRATIONS_JIRA_OAUTH_CLIENT_SECRET=%%REPLACE_IT_WITH_THE_CLIENT_SECRET_OF_YOUR_APP%%
INTEGRATIONS_JIRA_AFTER_AUTHORIZATION_REDIRECT_URL=https://%%REPLACE_IT_WITH_THE_DOMAIN_NAME_OF_YOUR_YLEM_INSTANCE%%/jira-authorizations/{uuid}/?justConnected

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".

Using API integration, Atlassian API, and PAT

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).

Step 1. Create Personal Access Token (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:

Step 2. Creating API Integration and sending requests to it from Ylem pipelines

As soon as you have your PAT configured, you can use it as an Access Token for POST/GET requests to Atlassian API.

As the first step, you need to go to the of Atlassian and create your own "OAuth 2.0" application.

Check and create a Ylem with it:

Now you can call it directly from the Ylem pipelines with the necessary query parameters and headers using the task.

💡
Developer Console
Atlassian REST API reference
API Integration
API_Call
below
Using Personal Access Tokens | Atlassian Support | Atlassian Documentation
Logo