Ask Your Question
0

Why is the recently created permission group in Azure DevOps not appearing in the assignment of Repository security?

asked 2023-07-15 09:53:31 +0000

ladyg gravatar image

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2023-07-15 10:00:02 +0000

scrum gravatar image

There are a few possible reasons why a newly created permission group in Azure DevOps may not be appearing in the assignment of Repository security:

  1. The group may not have been added to the appropriate security namespace.
  2. The group may not have the necessary permissions to access the repository security settings.
  3. The group may not have been saved properly after creation.
  4. The group may not have been added to the project or organization where the repository is located.
  5. There may be an issue with the Azure DevOps platform.

To resolve the issue, it is recommended to check the group's permissions, ensure it is saved properly, and verify that it is added to the correct security namespace, project, or organization. If the issue persists, contacting Azure DevOps support may be necessary.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss

Add Answer


Question Tools

Stats

Asked: 2023-07-15 09:53:31 +0000

Seen: 9 times

Last updated: Jul 15 '23