In Azure DevOps, we are trying to start a deploy to an environment. According to the policy, one approver must approve this.
After a person has given approval, the deploy is not started and Azure Devops keeps saying that at least 1 approver must approve. See the screenshot below, which shows that contradictory information is given. (A second approver also opened the page, by the way, but did not have the option to give approval... Probably because it was already given and so all approval requirements are met.)
We also tried changing the configuration, such that not one person in the list but rather a person in a group had to give approval. The same problem occurred, as seen in the screenshow below.
Does anyone know what could be wrong here? The information from Azure DevOps is contradictory with itself.
(Interesting detail is that this has worked until recently. We have no idea why it's suddenly broken.)
Please Click the "TST" resource to check the advanced setting, check if enable the "Allow approvers to approve their own runs".
And try to remove it and create a new "Approvals and checks" and to check if it works.
For more information, you could refer to approvals.
Related
My colleague submitted a pull request on a repository. I made a recommendation on renaming a function but I clicked "Approve with recommendations". However, from here I cannot do anything. I cannot "Complete" the pull request. The Complete button remains disabled.
We made a team and we gave the team Project Contributors. WHat else do we need to do? I've used Github for years and I cannot figure out why Azure DevOps UI is so terrible.
Do you have any merge conflicts in the pull request? Make sure to resolve them first.
Also, make sure that your user is not part of any group that has a Deny-policy possible overriding your Project Contributor rights.
Lastly, check the branch policies (link) to see if anything is hindering you from completing the request.
Is there anyway in Azure DevOps to forbid people from adding/removing required reviewers when creating a Pull Request?
I have set up the policy "Automatically included reviewers" with a bunch of required reviewers.
But still anyone who create a PR can easily add someone else in the required reviewer list or remove anybody from the automatically included required reviewer.
I want anyone to create a PR but not add/remove any required reviewer.
Apparently this is not possible, and they don't seem to consider it a bug. See this feedback item. I think it is ridiculous that they don't consider this a bug. When you set a branch policy stating: Pull requests to this branch van only be completed when these reviewers have reviewed it, only people having the permission Bypass policies when completing pull requests should be able to complete the pull request without adhering to the policies, which includes the required reviewers policy.
I've added a new feedback item to stress this. Feel free to update this feedback item, however history tells me they will either acknowledge the issue and never fix it, or still deny it is a bug.
We probably will we have to learn to live with this bug
If a required reviewer is added via Automatically included reviewers, the reviewer can't be removed:
For reviewers added manually or via the API there's no way to forbid it as far as I know.
The following feature requests implicitly confirms this:
https://developercommunity.visualstudio.com/t/Users-able-to-change-required-reviewer-t/1196519
When a user hits Resolve on a review comment I made in a PR, I would expect to see a notification in my emails but I do not seem to be getting them.
Here are the options available to me in DevOps:
Here are the options assigned to my user:
For reference, this is the section I'd expect to get updates for when set to Resolved:
I'd imagine it to work similar to how it works in GitHub. Currently I'm relying on team members to #mention me.
I am an employee of an organization. Could it be that the option has been removed from me in some group policy?
Could it be that the option has been removed from me in some group policy?
I am afraid there is no such specific settings to get the notifications for Azure DevOps PR review comment set to resolved.
We could only defined the notification for the Pull request changes. But the default and supported notifications and supported event types do not support to check the state of the PR review comment.
You could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
We have created a field in all Work Items, named "Manager" to assign the Manager of the developer/tester, to whom the work item is assigned to. Now that person in the Manager field is not getting any email Notification when the assignee updates the work item.
Tried setting the notification, but creating notification for every work item is not feasible.
I tried with setting rules, but doesn't seem to have the right conditions and actions available.
I read about third party tools like power automate. Before jumping into that solution, I would like to know if this can be achieved with the existing configuration settings in Azure Devops
I would like to know if this can be achieved with the existing
configuration settings in Azure Devops
I am afraid that azure devops currently does not provide built-in configuration settings to achieve this requirement.
You could add your request for this feature on our UserVoice site , which is our main forum for product suggestions. After suggest raised, you can vote and add your comments for this feedback. The product team would provide the updates if they view it.
Issue:
"The user doesn't have access to the variable groups added to this pipeline or they are not found. IDs: 3"
When this happens:
Migrating a Pipeline in "Json" format from "Azure DevOps On-premise 2020" towards "Azure DevOps Cloud".
When saving all changes is complaining that no access for the user towards "Variables Groups" that seems to be counter-intuitive because those were created with my user while doing the Import, i.e did create the same "Variables and Values" for the consumption of the Pipeline
Solutions Offered and Applied:
Some documentation indicated to do the next:
"So you just need to add "Project Collection Build Service(xxx)" account as Administrator role for the variable group."
I followed this and added the "Project Collection Build Service" from "read" to "Administrator" but the same error output is presented.
This is not definitively an answer, but one thing to check is whether or not access is allowed to all pipelines:
I don't see that checkbox in your screenshot. If Allow access to all pipelines is not set, or not settable, Microsoft recommend manually queueing a build - if there's a resource authorization error, you should be able to select it and authorize access to the pipeline that's being executed.
State:
Solved
Solution Details:
It seems MS/Azure DevOps hashed each link to a variable group dependant on the Collection, so when migration takes place the current links migrated are completely useless,
The right action would be in that sense to undo the links are re-create them from scratch again.
This will save a lot of time for other folks with the same issue, enjoy!