Mend for Azure Repos - Common Issues

Overview

This article details common issues with the Azure Repo Integration and provides potential solutions to those issues.

Invalid PAT in the Mend application

You might see this error message in the Mend application when saving the PAT. It most likely indicates that the PAT’s organization was not set to the All accessible organizations option.

An onboarding or remediation pull request wasn’t created in the integrated repo

There can be several reasons for such behavior.

1. Make sure that the bot-user has access to the project

This is especially important to remember when a new project is created in the organization. By default, bot-user will not get access to the new projects and you have to do it manually in the Organization Settings → Users. Click on three dots on the bot-user and go to “Manage user”

There you can provide access to the new project. Keep in mind that the bot-user should get a “Project Administrators” access level. Also, after the bot-user gets access to the new project, sync must take place, as described here.

2. Make sure that projects are synchronized

When one of the following actions happens the integration should be synchronized:

• Bot-user received access to a new organization

• A new project was created in the organization

• PAT updated

You can find more information about this here.

3. PAT might have expired

For information on how to deal with this, see the bot-user documentation.

4. Make sure that the pull request actually wasn’t created

Your pull request might have been actually created, but you didn’t look in the right place.

By default, when you open the Pull requests page in Azure Repos the “Mine” tab will be opened. This tab will show only those pull requests that were created by the logged-in user.

But if the integration relies on the bot-user’s PAT, all pull requests that Mend will create in the integrated repositories can be found in the “Active” tab.