Jira integration

Link Discoveries to Jira issues and stay synced with your software team.

Valentin Huang avatar
Written by Valentin Huang
Updated over a week ago

Our Jira integration lets you create and link issues of all types right from your Harvestr Discoveries. You will then be able to follow the evolution of these issues and their status in Jira, without leaving Harvestr. 

Prerequisites

In order to use our Jira integration, all you need is:

  • a Jira account with Jira Administrator permissions

  • a Harvestr Editor account

How to integrate Harvestr to your company's Jira account

1. Connect your Jira account

In order to connect your Jira account to Harvestr, go to the Jira section of your Harvestr integrations settings. From there, you will be able to enter your Jira Base url which should be something like yourcompany.atlassian.net

2. Login to Jira as administrator

In Jira now, Choose > Products. Select Application Links in the left menu. You can find more information on how to create Application Links in Jira here.

Select Create link.

Choose Direct application link.


In the field 'Application URL', enter https://app.harvestr.io and click 'Create new link'. 

If you get a warning saying that 'No response was received from the URL you entered...', do not pay attention to it and click on 'Continue'.

3. Fill in the "Link applications" popup form

You will now have to fill a few fields to set up the integration. Here are the fields : "values" you need to enter:

Application name : "harvestr"

Application type : "Generic Application"

Service provider : "harvestr" 

Consumer key : "harvestr" 

Shared secret : "harvestr" 

Request token url : "https://app.harvestr.io

Access token url : "https://app.harvestr.io

Authorize url : "https://app.harvestr.io

Finally, check the "Create incoming link" box and press 'Continue'.

You will then have to enter three more values:

Consumer key: "harvestr" 

Consumer name: "harvestr" 

For the Public key, copy and paste it from the Jira section of your Harvestr integrations settings.

You should see the following message in Jira : "Application link 'Harvestr' created successfully".

4. Finalize the connection to Jira

You’re now ready to authorize Harvestr access to Jira. Go back to the Jira integration settings in Harvestr and click on "Connect to Jira" at the very bottom of the page.

This will pop up a last window where you will just need to allow Harvestr access to your Jira project.

Once this is done, you will be automatically redirected to your Jira integration settings in Harvestr and you should see the confirmation that "Your Jira account is connected".

How to use the Jira integration in Harvestr

Now that the integration is set up, you will see a Jira section appear in each and every Discovery in Harvestr.

You will now be able to :

  • create and link one or more new Jira issues to a Discovery

  • link one or more existing Jira issues to a Discovery 

1. Create and link one or more new Jira issues to a Discovery

Once you have decided to launch a Discovery to production, you can create issues in Jira that correspond to what needs to be developed.

When you press "Create issue" in a Discovery in Harvestr, it pops up a window where you will be able to enter the attributes of the issue you want to create, namely its:

  • project

  • board

  • sprint

  • type

  • status

  • assignee

  • summary

  • description

Pro tip: by clicking on "Copy fields from Discovery", you can automatically copy the title and description fields from your Discovery and paste them in the Summary and Description fields of the issue.

Once the issue is opened, it will be created in Jira with the attributes you have entered and with an additional link to the Discovery in Harvestr. This gives your software team access to the valuable content that's in your Discovery, like user feedback for example.

In your Discovery in Harvestr, you will also have the link to the newly created issue and you will be able to keep track of the evolution of its statuts in Jira.

2. Link one or more existing Jira issues to a Discovery

Sometimes, you will also want to link Jira issues that already exist to a Harvestr Discovery.

You can do that by clicking on the "Link issue" button in your Discovery. This will open a search bar where you will be able to search a Jira issue by its name or by its key. The search by key only works when you type the exact entire key in the search bar.

Once you have linked the issue to your Discovery, you will also be able to follow the evolution of its status from Harvestr.

Note: you can link as many issues as you like to a Discovery.

3. Keep track of linked Jira issues and sync Discovery statuses with issue statuses

Adding the "Jira issues" field to your Discovery views

The best way to keep track of the status of issues that are linked to your Discoveries is to add the dedicated Jira issues field in your Discovery table.

You will then see which Discoveries are linked to a Jira issue or not and you will also see the status of these issues right from the Discovery table.

Last but not least, click on the issue tag to open the issue in Jira.

Filtering Discoveries by Jira issues' parameters

In your Discovery views, you will then be able to filter Discoveries based on parameters of linked Jira issues.

Here are some views that you can build to keep track of issue statuses and update Discovery statuses accordingly :

In Jira view: a view that displays all Discoveries that have at least a linked Jira issue (filter -> Jira : Is not empty)

In Jira Shipped view: a view that displays all Discoveries that have the shipped status in Jira (filter -> State name contains: your shipped status in Jira). From this view, you can then bulk select all Discoveries and update their status to shipped in Harvestr as well.


If you have requests or ideas about how we could improve our Intercom integration to fit your workflow better, shoot us a message!

We also provide custom integrations with Trello, Github, Gitlab and Figma to help you stay synced with your engineering and design teams. 

Did this answer your question?