Setting up a Jira Full Sync integration for Jira Server

← Back to Jira section

• Availability
  • Plan: Ideas Advanced
  • On a legacy plan? Click here for more info
• Roles and Permissions
  • Add: Admin, Editor
  • Edit: Integration Owner
  • Delete: Integration Owner

Use our Jira two-way integration to create a link between your ProdPad Ideas and User stories and your Jira issues to update them when there is a change in either tool. Changes made in any ProdPad Idea or User Story that is linked to a Jira Issue will update instantly when the Sync updates to Jira button is used. However, due to the nature of the sync, any updates made in the Jira Issue will take up to 15 minutes to reflect in the ProdPad Idea or User Story. This article will discuss how to successfully set up the Jira Full Sync integration between ProdPad and Jira Data Center and Server projects.

Our Jira integration supports Jira Cloud, Data Center and Server, and NextGen projects. If you are a Jira Cloud customer and you want to create a Full Sync integration – follow this setup guide. 

Step 1: Create the integration

Click on the Integrations icon at the bottom of the navigation bar. 

Once you land on the Integrations page, click the ' Create new' button and select Jira Server & Data Center from the Development menu.

You'll then be asked to choose the integration type. In this article, we'll be setting up a Jira Full sync integration. Select it and click Next to move to the next step.

Step 2: Name your integration and connect to your Jira workspace

First, give your integration a name. Try and choose something descriptive – it will help you and your team find it amongst other Jira integrations in your account. For example, use the name of the Jira project you'd be linking to followed by the sync type: 'My Jira Project (full sync)'.

Next, you'll be asked to enter your Jira workspace URL. This is your Jira application domain; it might look like https://www.yourcompany.com/jira/. Enter it in the text field and click Next to move to the next step.

Step 3: Authorize your connection

In this step, we will allow the two applications to connect and exchange data in order to keep everything synchronized. 

Setting up an Application Link in Jira

In a new tab, log in to Jira as an Admin and navigate to Application links: click the 'Settings' cog at the top right and select 'Products' in the dropdown, then click 'Application links' from the menu on the left.

Now go back to ProdPad and copy your public key (use the ' Copy' button to grab the key in one click).

Navigate back to Jira and paste the key into the '  Public Key' field. Be sure to copy and paste the whole key, including the BEGIN and END parts. Enter prodpad for Consumer Key and ProdPad for Consumer Name. Click Continue to move on to the next step. 

Once the application link has finished processing, you'll see a message confirming the successful creation of the application link in the bottom left-hand corner of Jira. 

All done! Head back to ProdPad.

Authorize your connection

Once in ProdPad, click the ' Authorize' button. If your application link was set up correctly, you will see the screen below; click Allow – now the two applications are connected and ready to exchange data.

Step 4: Connect to Jira project and choose issue types

In this step, you will choose a Jira project to connect to and configure the relationship between Jira issues and ProdPad Ideas and User stories.

First, select a project from the dropdown.

Then choose Jira issue types that would correspond with ProdPad Ideas and User stories.

For the best results with this integration, the mapping we recommend is: 

• A ProdPad Idea = A Jira Epic
• A ProdPad User story = A Jira story.

This would allow to have a parent/child relationship between the Jira issues created, similar to how User stories are linked to Ideas in ProdPad.

You can choose to map your Ideas to a base-level issue type in Jira (for example, Task), too – in such cases Ideas and User stories will appear in Jira as unrelated issues. Once you've finished setting up your mapping, click  Next to continue to the next step. 

Please note that mapping of Ideas is required – the integration will not work without it. However, if you do not want to push User stories into Jira, you may skip their mapping – just leave the default selection in the dropdown and move to the next step.

Step 5: Map Idea fields to Jira issue fields

Now let's map the fields on the Idea canvas in ProdPad to the issue fields in Jira. The options you see in the dropdowns will depend on the issue type you selected for Ideas earlier.

For the integration to work,  it is required to map Jira Summary field and any other fields marked as Required in your account. For convenience, the Idea fields will be automatically mapped depending on the Jira issue type option you selected for Ideas in the previous step, but the default mapping for these fields can be changed as required. To map other fields, use the 'Add mapping' button; you can map as many fields as you and your team need. You can remove additional field mappings by clicking 'X'.

Please note that full sync integration does not support mapping to multiple fields at this time. It means that for each Jira field, you can select only one option in the ProdPad field dropdown. Once you've finished setting up your mapping, click Next to proceed to the next stage of the integration setup.