Setting up a JIRA Integration

ProdPad has a direct integration available with JIRA.

The two-way integration between JIRA and ProdPad allows you to push any idea from ProdPad to JIRA, creating a link between the idea and the new ticket. You can map your Issue statuses in JIRA with the custom statuses in ProdPad, and so when the status is updated in JIRA, the change reflects in your ProdPad account where the rest of the team can see it.

Our JIRA integration supports JIRA Cloud, Server and NextGen projects.

Please review this JIRA Installation Considerations document before proceeding.

Getting the integration with JIRA set up is easy, and just requires you to follow these steps:

Part 1: Setting up JIRA integration in ProdPad
Part 2: Setting up an Application Link in JIRA
Part 3: Map to a JIRA Project
Part 4: Map Fields from JIRA
Part 5: Map Statuses for Syncing with JIRA
Part 6: Getting your team onboard
Part 7: Pushing an idea from ProdPad to JIRA


Part 1: Setting up JIRA integration in ProdPad

In your ProdPad account head to the Integrations page.


On the right-hand side of the page, select JIRA from the list in the available development tools options.


In the "New JIRA Integration" page, give your integration a name (this is to help you and your team identify your integration later, which is useful if you’re planning on integrating with more than one other service), and enter the base URL.

The Base URL should be the domain and base of your JIRA application. JIRA OnDemand might look like and a self-hosted JIRA install might look like

It is important to include the trailing slash and use https.


Click Create to move forward. Be sure to grab the public key that is shown, you will need this in the next step.  


If there is a firewall or have a selective block between the internet and your JIRA server, you’ll need to get the sysadmins to allow traffic from the IP addresses:


If you are using HTTPS then port 443 will need to be opened otherwise port 80 for HTTP.

Part 2: Setting up an Application Link in JIRA

Log in to JIRA and under JIRA Settings > Products > Application links



Enter into the field at the top of the "Configure Applications Link" page, and click Create new link. (hit continue twice after the warning)



In the "Link Applications" modal window, enter the following information: 

Name of your app: ProdPad 
Select Generic Application from the "Application Type" dropdown

Service Provider Name: ProdPad 
Consumer key: prodpad 
Shared secret: prodpad 
Request Token URL, Access token URL, Authorize URL:

Check the checkbox for "Create incoming link".



Click Continue.

From the integrations page in ProdPad, grab your public key, which you should copy and paste into the "Public Key" field in JIRA. Be sure to copy and paste the whole key, including the BEGIN and END parts.

In the following window, enter prodpad for the "Consumer Key" and prodpad for the "Consumer Name".



 Now that you have set up an Application Link in JIRA, you can head back to your partially completed integration in ProdPad and click 'authorize' to authorize with JIRA.

Part 3: Map to a JIRA Project

Now it's time to go back to ProdPad app. Find your integration, click on Edit Integration and authorize your login. Once you have completed the authorization, a list of all of your JIRA projects and issue types will be shown to you. Click to select one of these options.



If you need to push ideas in ProdPad to different projects in JIRA, set these up as separate integrations.

Part 4: Map Fields from JIRA

Once you’ve selected the Project and Issue type in JIRA, you’ll be shown a form that allows you to map the fields on the Idea canvas to the fields in JIRA.

The mapping will change whether you are using the issue type Epic or Story. The mapping allows you to select none, 1 or more fields from ProdPad to map to JIRA. To select more than one, simply hold CTRL and click on the multiple options in each field.

For an Epic, the suggested mapping is:

“Epic Title” => “title”
“Summary” => “description”
“Description” => “Business case, functional specs”
“Tags” => “Tags”
“Attachments” => “Mockups, Files”

For a Story, the suggested mapping is:

“Summary” => “user story”
“Description” => “acceptance criteria”

This assumes you are pushing ProdPad user stories to JIRA Story issue type. If you are planning to push ideas as user stories, then we suggest the following:

“Summary” => “Title, Description”
“Description” => “Business Case, Functional spec”

Once you have selected the mapping, submit the form by clicking Save Changes.

Tip: If there are any fields that aren't showing up, make sure that they are set to 'Visible on form' within your JIRA field options.

Part 5: Map Statuses for Syncing with JIRA

Once you’ve got your JIRA integration set up to this point, you get the option to map your Issue statuses in JIRA to your Idea statuses in ProdPad. That way, when you update the status of an issue in JIRA, the linked Idea in ProdPad is automatically updated.


You don’t need to match them all. If a status in JIRA is not matched, it will not change the status in ProdPad. You can also create custom statuses under your workflow options.

Click 'Save Changes' to save your settings.

Part 6: Get your team on board

To make it easy for your team to use the same integration mappings, you can share your integration with your team.

In your Integrations list, click the 'Shared with team' setting.


Once this is done, anyone in your ProdPad account can log in and go to the Integrations & API page, and select the original integration in the 'Available Integrations' list.


Part 7: Pushing an idea from ProdPad to JIRA

Now that you've got an active, 2-way integration with JIRA set up, it's time to start pushing finished ideas from ProdPad to JIRA.

Head to your Ideas List, and pick an idea that's ready for development. In the Idea Canvas page, click on Push This will open up a modal window where you can choose to push the Idea via the JIRA integration you've set up, or any of your other integrations.

You will also be prompted to push over user stories. If you chose to do so, any associated user stories will be pushed to JIRA as a user stories and associated to the Epic that the idea becomes (assuming the issue type selected for the JIRA integration is Epic).

If you have any required fields, you will be asked to enter them before pushing.



On the Idea Canvas now, there will be a link to the JIRA ticket in the 'Links' section, and the ticket in JIRA will link back to the ProdPad idea.


If you have configured the Status Mapping in Part 6 of this guide, any changes to the issue status in JIRA will automatically update the Idea status in ProdPad as part of the JIRA 2-way integration.


Looking to add multiple projects?

If you wish to setup another project within JIRA, simply repeat the steps above. You may set up as many integrations as you like - and as long as they're the same account (base URL) they will only count as one integration. 


  • Avatar
    Gaurav Kotak

    Hi, this article is helpful. Some of the images seems to be missing. I do have a question here - can we automatically create stories in JIRA based on ideas in prodpad - but only those whose status = queued for development?


  • Avatar
    Andrea Saez

    Hi Gaurav,
    At this time you cannot set it so that ideas with a certain status are pushed automatically, but you can push them on a case by case basis with that particular status.

  • Avatar
    Glen Ford

    Based on the description here and my own experience, ProdPad never updates a ticket in Jira. Choosing "Push…" again just creates new tickets. For my purposes, that means either the spec at every level has to be completely figured out before being published to Jira (which seems pretty unrealistic in an agile world), or ProdPad is not the canonical system of record for requirements once an Idea is sent to Jira. (I suppose the third possibility is that requirements have to be edited in both places as they evolve. This means ProdPad wouldn't be any easier than Google Docs or Confluence as a RMS.)

    Am I missing something?

  • Avatar
    Andrea Saez

    Hi @Glen,
    As the documentation outlines, pushing from ProdPad to JIRA will push the idea from your ProdPad account to your JIRA account, but it will not update any existing JIRA tickets. The integration is meant to create a link between ProdPad and JIRA for all ideas that are pushed over using the integration only.

    The integration is flexible enough so that you can select which fields are mapped over, and all of that info is pushed over to your JIRA instance, with only the status syncing back. No further information is then pushed from either instance (status only) in order to prevent any important information from being re-written. You can, however, always push additional User Stories as requirements evolve for that particular idea, which will link to the same Epic or Story you created from the idea.


  • Avatar
    Angus McDonald

    Can I use a modified version of this integration to push Feedback from a JIRA "Suggestions" project to ProdPad?

  • Avatar
    Andrea Saez

    Hey Angus,
    At this time the integration works from ProdPad to JIRA, not the other way around, and only for ideas/user stories.

  • Avatar
    Eric Merriman

    So for an integration best practice, do you recommend setting up the JIRA integration and using that to import ideas? I had imported my backlog from a csv file exported from JIRA. Then I set the JIRA integration. I assume no status linking will occur there. Is it different if I use the integration to somehow import?

  • Avatar
    Andrea Saez

    If you're bringing things in, it's definitely best to do so as a CSV like you did. This will give you the chance to reassess those ideas and make sure that they're still valid. If they are, then you can send them back to JIRA with all the relevant information and with the link back to ProdPad.

  • Avatar
    Maziar Ebrahimi

    Hi there,

    I have integrated Prodpad with a classic Jira project and set up the mapping of the workflows. I'm facing the below problems, would be grateful to have a response for them?
    - During the workflow mapping I see in my Jira workflow, steps that I have not set up in my workflow as a step, where could these steps come from?
    - When I update the workflow of a story in Jira nothing is reflected in Prodpad workflow. I played a lot with many cases but it seems nothing passes through from Jira to Prodpad side. The link as well doesn't work from Prodpad side to Jira side.

    - It is possible to push one story/EPIC from Prodpad to Jira more than one time. In this case for 1 Prodpad ticket, there will be more than 1 ticket in Jira. In case the above problem is resolved and status updates from Jira--> Prodpad works, how does Prodpad react in the case that the two stories in Jira linked to 1 story in Prodpad have different statuses? i.e. One "In Development" the other "DONE"?

  • Avatar
    Chip Ach

    It looks like some of the ProdPlan terms have changed (e.g. "Tags" are now "Labels" and more), so you might want to update this documentation to match.

  • Avatar
    Andrea Saez

    Hi Chip, ProdPad has not changed its naming convention. Tags have always been tags. Labels are what comes through from JIRA, and we allow you to sync tags to JIRA labels.

  • Avatar
    Brian Pollard

    Ideas come from across our organization and can range from new product ideas, new features, or small enhancements to existing products. Ideas not only range from large to small, but also will be written with different levels of detail. Ideas need to then be reviewed and groomed by Product from a customer/business value, feasibility, scope, user, etc. perspective.

    If Product grooms the ideas, by updating the idea, they may loose their original creators messaging intent. So it seems Product should leave PP Ideas intact and only groom Stories associated with am Idea. In this case the Stories really should be called Features or Capabilities since user stories are what Agile Scrum teams will work on within a Sprint. Roadmap cards should then be identify a capability or set of features that are planned. 

    Is there are way to bring over PP Roadmap Cards as an Epic in Jira, and the PP Stories as a sub-Epic? This is needed so that scrum teams can decompose Epics into User Stories once in Jira.

    Also, the one-way one-time integration to Jira really seems to block Agile process where the business and development teams need to manage change. Since Product Managers will manage roadmap items in PP and then need to decompose epics/stories into Jira that fit into 2 weeks Sprints, Product Managers need to now use two pieces of software to groom requirements instead of managing completely from ProdPad. A two way integration should be something that is configurable so that the ProdPad philosophy of final requirements in ProdPad is not forced. In reality, business and technology teams need flexibility to manage change.

    Edited by Brian Pollard
  • Avatar
    Andrea Saez

    Hi Brian, I'll create a ticket for you in our system to follow up.