Setting up an Azure Devops Integration

← Back to Azure Devops section

Setting up an Azure Devops Integration

ProdPad has a direct integration available with Azure Devops (formerly known as Visual Studio Team Services/VSTS).

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

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

Part 1. Setting up an Azure Devops integration
Part 2. Mapping Fields
Part 3. Pushing ideas to Azure Devops
Part 4. Sharing with your team

Part 1. Setting up the Azure Devops integration in ProdPad

To start, log in to ProdPad as an Admin, and head to the Integrations page.

On the module page, click on +Create Integration and select Azure DevOps to get started.

Enter a name for the integration e.g. ADO Dev Queue and and a quick description, then click Create.

If you aren't already logged into Azure DevOps, you will be prompted to enter your credentials. Once you're logged into Azure DevOps you’ll be prompted to allow ProdPad limited access to your Azure DevOps profile. We require access to read your organizations and boards; create and update cards, lists and boards; and make comments on your ideas.

Please note this integration only works with Azure DevOps .

Once you're logged into Azure DevOps you’ll be prompted to allow ProdPad limited access

Part 2. Mapping fields

Once the authorization is complete, you will be able to select a project from your Azure Devops account. Select the project you want your ProdPad ideas to appear in once they've been pushed to Azure Devops.

Map your fields from ProdPad to Azure DevOps

Next, it's time to map your fields from ProdPad to Azure DevOps.

In this step, you'll pick which fields from your Ideas page you want to send to Azure DevOps. At the very least, you need to select something for the Name field in Azure Devops – we recommend using the Title field from your ProdPad idea for this. You can also pre-fill the Description in your Azure Devops issue with the description, business case and functional specs in ProdPad, or any combination of them.

Finally, you can set your field mapping to include mockups and files from ProdPad, which will be added as Attachments to your new card in Azure Devops, once you push.

Set your field mapping to include mockups and files from ProdPad

The last step is to map statuses, so that as the issue moves within the development workflow, ProdPad will reflect those changes.

Map statuses, so that as the issue moves within the development workflow

Part 3. Pushing ideas to Azure Devops

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

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

Part 4. Sharing with your team

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 'Teamwide' 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.

Top Tip

Looking to add multiple projects?

If you wish to setup another project within Azure Devops, 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.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us