According to Microsoft's document, a project could be deleted from the Overview menu of Project settings. but in my own on premise Azure Devops 2019, there is no Delete button at all.
Does anyone know any solution?
screenshot:
If you are not a member of the Project Administrators group, the Delete project column will not be displayed.
If you want to have permission to delete the project, you need to be added to the Project Administrators group in project settings or Project Collection Administrators group in organization settings.
You can also delete the project in the Projects of organization settings，see if this is feasible.
Related
In case a project and organization got deleted by mistake, How to recover deleted project and organization in Azure DevOps?
If your project or organization is deleted within 28 days, you can recover it in a few steps.
For organization, I advise you to check Microsoft documentation.
For projects, it is very simple, regarding Microsoft documentation.
Click on Organization settings
Click overview and there is a category called Recently deleted projects with a list of projects that you can recover.
Enjoy.
I'm trying to add a new repository to my project but don't see the option. I have 5 projects and all of them I am able to, any reason why not here?
Here I see the "add" option:
But here I don't:
Your current account does not have the permission to delete or add new repositories under your current project called Homeazzon.
Please enter Homeazzon project-->Project Settings-->Repos-->Repositories-->Security
check every Azure Devops Group and User and then set Create repository and Delete repository to Allow.
I have one older project in my Azure DevOps organisation that does not have this "project Build Service" account in Project Settings=>Repos=>Security. If I create a new project in my organisation then I can get it there just fine.
How could I get that project Build Service account to my older projects as well?
How could I get that project Build Service account to my older projects as well?
I am afraid there is out of box way to get that project Build Service account to your older projects.
As workaround, you could add a group for that project Build Service account on the Organization Settings->Permissions, add members in that group.
Then, go to Project Settings->Teams->select the Team project-> Add users and/or groups:
After that, we could search that group in the Repos=>Security, do some change in the permission and save it:
Hope this helps.
I have in Azure Devops one project with a lot of developer teams. Our Cloud Platform team uses a different project to create artifacts with ARM templates as result of a build pipeline.
How do I grant access to these artifacts for all my developers at group level? At the second project I can create a new group with View project-level information permissions. But I can only add users, not groups from that project.
Anyone any ideas?
When you add other project groups to the newly created group, do you receive the following error message?
If so, we can make clear from the error message that this is by design, auzre devops does not support adding groups of different projects to the group.
If you want to add a group as a member to the group you created, then the added group needs to be organization-level. Only organization-level groups can be added to project-level groups.
I'm using VSTS on Visualstudio.com to host our Solution. I have one solution with multiple Visual Studio projects, all hosted in a Team Project inside TFS. Now I'll have some one to help me with development, but I don't want him to have access to all the Visual Studio projects, only some of them. How can I give him access to some of the Visual Studio projects while denying access to the other ones?
If you are using TFVC as source control, you can refer to these steps below:
Add the user to your VSTS
Go to the admin page of that team project
Select Security tab
Click Create group to create a new group (e.g. CodeGroup)
Set View project-level information to Allow in Permissions tab
Add the corresponding user to that group in Members tab
Click Version Control tab
Select the folder of the project (one of the project in your solution folder)
Click Add to add CodeGroup (step4)
Set Read and Check in permissions to Allow
If you are using Git as source control, you can’t set the security for an item (project in a solution) in the repository.
On the other hand, If there are some project references that the user can’t access, I recommend that you can package and push the assembly to the feed of your VSTS: Package Management in Team Services and TFS