In this article, you can find information on possible reasons for the disabled list of repositories on the Azure DevOps branch creation modal in Jira.
Before you check access levels
The repository field looks the same - empty and disabled, with no explanation - for a couple of other reasons too. Rule these out first, since changing an access level won't help if one of these is the actual cause:
-
No project has been selected yet in the Create Branch dialog. The repository list only populates once a project is chosen - this is expected, not an error.
-
The dialog is showing a "No access to Azure DevOps" banner. If so, the connection itself has a problem (an expired or invalid token, a wrong scope, or a wrong domain URL) - see How to fix "No access to Azure DevOps" error when creating a branch?. That's a different fix from the one below.
If a project is selected and there's no "No access" banner, the most likely remaining cause is the user's Azure DevOps access level, covered below.
Access level
Check the access level of the particular user. To be able to create branches, the user must be granted a Basic access level or greater.
Users granted Stakeholder or lower level to private projects have no access to source code. Otherwise, users granted Stakeholder access to public projects have the same access as Contributors and those granted Basic access.
To change the access level for the particular user, organisation owner (admin) needs to:
-
In the Organization settings page, open the Users section.
-
Find the user whose access level you want to change. Select Manage user.
-
Depending on the organization's setup, they may have options such as Basic, Stakeholder, Visual Studio Subscriber etc. Choose the Basic access level.
-
After selecting the new access level, select Save.
To learn more, see About access levels.
Updated: April, 2024