LaunchDarkly Developer Documentation

Get started in under 30 minutes.
LaunchDarkly provides feature flags as a service for Java · Python · Ruby · Go · Node.js · PHP · .NET. Control feature launches -- who sees what and when -- without multiple code deploys. Easy dashboard for phased rollouts, targeting and segmenting.
Need more help? write us at support@launchdarkly.com

Get Started    Guides

LaunchDarkly's Jira add- allows you to link your feature flags with your team's Jira issues. When a feature flag is turned on, off, or has it's targeting rules updated, it's associated Jira issue pages will display the flag's current status.

Installation and configuration

The LaunchDarkly for Jira app into your Jira Cloud intance via the Atlassian Marketplace

The Jira app makes use of LaunchDarkly webhooks to send feature flag updates to your Jira instance. Once the app is installed, you'll need to create a personal API access token with create and delete access to webhooks. This can be done by either creating a token with "Writer" level access or above, or by using a custom role .

If you're using a custom role, a valid configuration would look like this:

Now that you've created an access token, use it to configure the Jira integration for your LaunchDarkly account. Visit your Jira instance's add-on management page, and click the "Configuration" button for the LaunchDarkly app.

From that page, you should first set your API key. Again, create this key with Writer level access, Admin level access, or with a custom role. Then you can select which environment the app will track for each of your LaunchDarkly projects. By default, the app will track your production environments:

Environment selection

If selected environments are reconfigured after issues have already been associated with flags, the existing connections will display the environments they were historically connected to until the next time that flag is updated. New flag connections will display the flag configuration for the updated environment.

Once the LaunchDarkly for Jira App is set up, you should see a "Releases" panel when viewing your issues through the "Active sprints" board. If no flags are currently associated with an existing Jira issue, you'll see a button to add one. If you already have one or more flags associated with a Jira issue, you'll see the rollout status of each connected feature flag on each Jira issue.

Now that the Jira app is configured and ready to rock, it's time to start link our feature flags to our Jira issues.

Releases panel must be enabled

The Jira issue view, which contains the release panel, is a per-user setting. If it is off you will not see the release panel. You can reference this in Jira's documentation here.

Creating a new feature flag from a Jira issue

To create a new flag with Jira issues, navigate to your Jira issue's feature flag panel, click "Add feature flag", and select the "Create feature flag" option:

You'll then be redirect to the LaunchDarkly flag creation page, where your selected Jira issue will be automatically pre-populated:

Connecting an existing feature flag to a Jira issue from LaunchDarkly

If you're ahead of the game and already created a feature flag for your Jira issue, you can add a Jira issue to your existing flag by creating a custom property for your flag of type "Jira issues", and entering a list of Jira issue keys as the property value:

Adding issues to an existing flag

Your Jira issue must exist before you associate it with your feature flag. If you accidentally added a Jira issue to your flag, delete the custom property, create your Jira issue, and try again.


Jira


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.