Mazaal AI Logo
Get Extension
AppsPricingBlogTry it
Jira logo
LaunchDarkly logo

Connect Jira to LaunchDarkly

Build an AI agent that works across Jira and LaunchDarkly, on a schedule or when you click Run.

24 source actions
10 target actions
Reverse direction supported
Start buildingHave us set it up (A$490)Browse Jira integrations

Why Connect Jira & LaunchDarkly?

Read what you need from Jira

Your agent uses Jira's documented actions to pull the records it needs, each time it runs.

Run a LaunchDarkly action

Then it uses one of 10 documented actions, such as Evaluate Feature Flag, Get Feature Flag, Get Feature Flag Status.

Test it, then put it on a schedule

Run it once on your own data and check the result. Then set it to run daily, on weekdays or weekly.

Available Triggers & Actions

Jira logo

Jira

Triggers (4)

New Event

Emit new event when an event with subscribed event source triggered, See the documentation

webhook
New Issue Created Event (Instant)

Emit new event when an issue is created. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Deleted Event (Instant)

Emit new event when an issue is deleted. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Updated Event (Instant)

Emit new event when an issue is updated. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook

Actions (24)

Add Attachment To Issue

Adds an attachment to an issue. See the documentation

Add Comment To Issue

Adds a new comment to an issue. See the documentation

Add Multiple Attachments To Issue

Adds multiple attachments to an issue. See the documentation

Add Watcher To Issue

Adds a user as a watcher of an issue by passing the account ID of the user, For example, 5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentation

Assign Issue

Assigns an issue to a user. See the documentation

Check Issues Against JQL

Checks whether one or more issues would be returned by one or more JQL queries. See the documentation

Count Issues Using JQL

Provide an estimated count of the issues that match the JQL. See the documentation

Create Custom Field Options (Context)

Create a context for custom field options. See the documentation.

Create Future Sprint

Creates a future sprint. See the documentation

Create Issue

Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. See the documentation

Create Jira Version in Project

Creates a project version. See the documentation

Delete Project

Deletes a project. See the documentation

Get All Projects

Gets metadata on all projects. See the documentation

Get Board

Returns the board for the given board ID. See the documentation

Get Cloud ID

Gets the cloud ID and details of all accessible Jira Cloud sites. See the documentation

Get Current User

Returns the authenticated Jira user's account ID, display name, email, and active status. Call this first when the user says 'my issues', 'assigned to me', or needs their Jira identity. Use the returned accountId with **Search Issues with JQL** (e.g. assignee = '{accountId}') or **Assign Issue**. Requires a Cloud ID to identify the Jira site. See the documentation.

Get Issue

Gets the details for an issue. See the documentation

Get Issue Picker Suggestions

Returns lists of issues matching a query string. See the documentation

Get Issue Types

Gets the available issue types. If a project ID is provided, returns issue types for that project. Otherwise, returns all issue types accessible to the user. See the documentation

Get Sprint

Returns the sprint for a given sprint ID. See the documentation

Get Task

Gets the status of a long-running asynchronous task. See the documentation

Get Transitions

Gets either all transitions or a transition that can be performed by the user on an issue, based on the issue's status. See the documentation

Get User

Gets details of user. See the documentation

Get Users

Gets the details for a list of users. See the documentation

LaunchDarkly logo

LaunchDarkly

Triggers (3)

New Access Token Event

Emit new event when a new access token activity happens. See the documentation.

webhook
New Flag Event

Emit new event when flag activity occurs. See the documentation.

webhook
New User Event

Emit new event when user activity is noted. See the documentation.

webhook

Actions (10)

Evaluate Feature Flag

Evaluates an existing feature flag for a specific user or in a general context. See the documentation.

Get Feature Flag

Get a feature flag by key. See the documentation.

Get Feature Flag Status

Get the status of a feature flag. See the documentation.

Get Project

Get a project by key. See the documentation.

List Environments

List all environments. See the documentation.

List Feature Flags

List all feature flags. See the documentation.

List Members

List all members in an account. See the documentation.

List Projects

List all projects. See the documentation.

Toggle Feature Flag

Toggles the status of a feature flag, switching it from active to inactive, or vice versa. See the documentation

Update Feature Flag

Updates an existing feature flag using a JSON object. See the documentation

Integration Features

24 documented Jira actions
10 documented LaunchDarkly actions
Plain-English agent instructions
Daily, weekday or weekly schedule, or run on demand
Execution monitoring
A supported LaunchDarkly to Jira direction

Capability Examples

Jira trigger → LaunchDarkly action

Catalog example
JiraJira

New Event

LaunchDarklyLaunchDarkly

Evaluate Feature Flag

LaunchDarkly trigger → Jira action

Reverse direction
LaunchDarklyLaunchDarkly

New Access Token Event

JiraJira

Add Attachment To Issue

How It Works

1

Connect Apps

Authenticate your Jira and LaunchDarkly accounts

2

Describe the Job

Say what to read from Jira and what to do in LaunchDarkly

3

Choose an Action

Select the documented LaunchDarkly operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Scheduled or On-demand Runs

Runs daily, on weekdays or weekly at a set time, or when you click Run. It does not fire on live Jira events yet.

Automated Actions

Use 10 documented LaunchDarkly actions each time the agent runs.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Describe the job in plain English. The agent picks theJira and LaunchDarkly actions it needs.

Your Own Accounts

You connect your own Jira and LaunchDarkly accounts. App connections need a paid plan.

Execution Review

Test the workflow and review provider responses before relying on it in production.

LaunchDarkly logoJira logo

Reverse Integration Available

Also connect LaunchDarkly to Jira for bidirectional automation

View Integration
Jira logo

All Jira Integrations

Explore all available Jira connections

View All Integrations
LaunchDarkly logo

All LaunchDarkly Integrations

Explore all available LaunchDarkly connections

View All Integrations

Popular Integrations

Notion logoNotion
Google Sheets logoGoogle Sheets
Airtable logoAirtable
Trello logoTrello
Calendly logoCalendly
OpenAI (ChatGPT) logoOpenAI (ChatGPT)
Anthropic (Claude) logoAnthropic (Claude)
Slack logoSlack
View all integrations →

More LaunchDarkly Integrations

Notion logoNotion
Google Sheets logoGoogle Sheets
Airtable logoAirtable
Trello logoTrello
Calendly logoCalendly
OpenAI (ChatGPT) logoOpenAI (ChatGPT)
Anthropic (Claude) logoAnthropic (Claude)
Slack logoSlack
View all LaunchDarkly integrations →

Ready to Connect Jira & LaunchDarkly?

Build this agent in Mazaal AI and test it on your ownJira and LaunchDarkly data.

Start building

Rather not build it yourself? We set up one Jira to LaunchDarkly agent on your accounts for A$490: a 30-minute call, a test on your real data, and 14 days of fixes. Plan billed separately. Email Enod