Integrate Jira

📘

Note

This is a third-party integration and is not an Optimizely subprocessor. See Optimizely's Third-Party Add-Ons & Platform Integration Terms.

Relevant products:

• Optimizely Web Experimentation
• Optimizely Performance Edge

Many Optimizely Web Experimentation customers also manage the development of features and experiments within Jira. This integration lets you connect your Optimizely Web Experimentation and Jira workflows without unnecessary duplication of effort by linking Jira issues to Optimizely Web Experimentation. Natively link Optimizely experiments to Jira issues. Then track their status directly from the relevant Jira ticket.

📘

Note

Optimizely Performance Edge is a lightweight experimentation product that delivers significantly faster performance than previous versions of Optimizely Web Experimentation. It does this by relying on a streamlined "microsnippet" which limits the range of available features.

Optimizely Performance Edge and Optimizely Web Experimentation integrate with Jira the same way, so all information contained in this article applies to experiments created with either version of Optimizely Web Experimentation.

This integration is only available on the Jira Cloud platform, and not on Server.

Set up Optimizely Web Experimentation for Jira app

Setting up your Jira application (app, sometimes called add-on or integration) is a three-step process:

1. Install the Optimizely for Jira integration from the Atlassian marketplace on the Jira instance. You will only have to do this once per Jira account.
2. Enable the Jira integration on each Optimizely Web Experimentation project where you want the integration to be available.
3. Connect the Optimizely Web Experimentation and Jira accounts of each user who will use the integration.

   📘

   Note

   Enable the Jira integration separately for each individual Optimizely project, but you only install the Atlassian marketplace app once for each Jira instance.

Configure the app in Jira

Configure this app before you use it. Your Jira administrator will have the appropriate credentials to do this.

1. Log in to your Jira instance as an administrator.
2. Install the Optimizely for Jira add-on by clicking the admin dropdown and choosing Add-ons (app).

Enable the app

1. Login to Optimizely Web Experimentation as an administrator or project owner in the Optimizely project where you want to use the integration.
2. Go to Settings in the left menu bar and click the Integrations tab at the top of the page.
3. Find and click Jira in the list of partners.
4. In the panel that displays on the right, toggle the switch to On.

5. Click Connect to Jira. This initiates the OAuth process. An Atlassian OAuth page displays. 
6. Select the Jira tenant URL you want to authenticate (for instance, company.atlassian.net), and click Approve.
7. Back in Optimizely, in the right panel under Integration Details > Settings, click Edit and select the same Jira tenant URL you just authenticated.

8. Click Save. Your Optimizely Web Experimentation project and your Jira instance are now connected.

Connect users' Optimizely and Jira accounts

Now that the integration is set up, other users are asked to authenticate their accounts with Jira to link actions to the specific user who performed them. Users only need to authenticate once in an account, but the integration must be turned on in each project individually. This ensures the appropriate Jira URL is associated with each Optimizely project.

Link an experiment to a Jira issue

1. In Optimizely Web Experimentation, find the experiment you want to link to a Jira issue and click ... at the far right-hand side. From the drop-down list, select Link Issue...
2. The Link Jira Issue window displays. A list of recently-viewed Jira issues is visible at the bottom. If the relevant issue is not listed there, enter the Jira issue key in the search field and click Search.
3. Click Save and Link Issue.

View Optimizely Web Experimentation information in Jira

The Optimizely Web Experimentation for Jira integration is visible to Jira users in your organization, whether they have access to Optimizely or not.

To find the Optimizely Web Experimentation information within a Jira ticket, open the ticket and scroll down the right side until you see the Optimizely logo for experiments.

To see information about an experiment: 

1. From within the Jira ticket, click Open Optimizely.
2. In the right-hand sidebar, click on either the Experiments or Ideas tab to display a list of linked experiments or ideas.

3. Click on the experiment or idea you want to view. Jira will display a summary of that experiment or idea.

For experiments, Jira users can see:

• Experiment type

• Status

• Date last modified

• Days running

• Experiment visitors

• Audiences

• Metrics

• Variation details

For ideas, Jira users can see:

• Score

• Owner

• Stage

• Site and touchpoint

• Hypothesis

• Linked experiment

Unlink an experiment or idea from a Jira issue

1. Find the feature you want to unlink and hover over the Jira ticket link. In the callout that displays, click Unlink.
2. If you are sure you want to unlink the Jira issue from the feature, click Unlink Jira Issue.

📘

Note

When you link or unlink an issue, that should be reflected immediately in both Optimizely and Jira.

Disconnect a user account

To remove user-level authentication between Optimizely Web Experimentation and Jira, follow these steps:

1. Go to the experimentation portal.
2. Log in to Optimizely Web Experimentation as the user whose authentication is to be removed.
3. From the Experimentation platform, go to Settings > Integrations.
4. Find and click on Jira in the list of integration partners.
5. In the panel that displays on the right, click Disconnect (next to the user avatar) and follow the instructions.

Troubleshoot issues 

The integration is not visible from inside Jira

If you have manually selected to use the old view in Jira, you will not be able to take advantage of this integration: you will have to enable the new Jira issue view in Jira. This will make visible the Releases section in each of your Jira issues.

1. Within Jira, click your profile avatar in the lower-left corner and select Personal settings.
2. Toggle the switch for the new Jira issue view.

📘

Note

If Personal settings is not listed as an option when you click your avatar, you can find the toggle switch under Profile instead.

To learn more about the new Jira issue view, see what is the issue view?

Verify your integration is functioning properly

There are two ways to verify your integration is working as expected. Go to Setting > Integrations and find the project integration settings for Jira. These should indicate that integration is switched on and connected with a Jira tenant URL.

Alternately, if you see the option to link or unlink Jira issues to feature flags in the Experiments, Ideas or Features dashboards, your integration is working correctly.

If it turns out that your integration is not working as expected, make sure your Jira administrator has installed the Optimizely Web Experimentation for Jira add-on before trying to authenticate from Optimizely Web Experimentation. Add this on the Jira side before making any authentication attempts.

Sometimes, the project settings show that Jira integration is enabled, but the option to link issues from the Experiments dashboards is not available. This means the user has not been properly authenticated. On the Atlassian oAuth page, select the same Jira tenant URL that is listed in the Optimizely Web Experimentation project settings.

If you cannot see the Releases section on the right side of your Jira issues, first make sure that New Jira Issue View is switched on in your Jira profile settings. If that does not work, check with your Jira administrator that the Optimizely for Jira app is installed in your Jira instance.

A Jira issue does not show up in Search

Possible reasons for this: 

• The issue does not exist or was moved to a different project and has a new key.
• Project integration settings do not have the Jira tenant URL that contains the issue.
• The user OAuth failed.