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.
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
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 https://yourcompany.atlassian.net/ and a self-hosted JIRA install might look like https://www.yourcompany.com/jira/.
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.
Note: 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.
Log in to JIRA and, in the Administration list (click on the cog icon in the top right), head to Applications.
Click on Application Links.
https://app.prodpad.com into the field at the top of the "Configure Applications Link" page, and click Create new link.
In the "Link Applications" modal window, enter the following information:
Name of your app:
Select Generic Application from the "Application Type" dropdown
Service Provider Name:
Request Token URL, Access token URL, Authorize URL:
Check the checkbox for "Create incoming link".
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".
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.
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.
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.
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.
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.