my company split into 2 and the visual studio online accounts, organization and project names are all pointed to the other company/domain of ours. I need to move/change these things to reflect the new company/domain. Anyone out there have a procedure to follow to change the VSO URL, organization and project names? It's imperative that I do not lose any source control history.
To rename your organization in Azure DevOps, you need at least Basic access and organization Owner permissions. And then go to Organization settings -- Overview to rename the organization:
Caution
The rename operation affects your organization's connections and
individuals who are currently working with your organization. Before
you start, find out what to do before and after renaming your
organization.
Detailed information, you can refer to the following link:
https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/rename-organization?view=azure-devops
To rename a team project, you need Rename project permission for a project. Select Project settings > Overview, and then enter a new name and select Save.
Useful links:
https://learn.microsoft.com/en-us/azure/devops/organizations/projects/rename-project?view=azure-devops
https://learn.microsoft.com/en-us/azure/devops/organizations/projects/faq-rename-project?view=azure-devops
Related
I'm trying to download my project from Visual Studio Online (TFS), but I can't see one project in list. I have two accounts, main and secondary. I'm trying to get project using secondary account. Both users have Administrator permission on this project. Also, other projects, that I see in list, have same permissions with this account. I see this project on web-site (my_organization.visualstudio.com), but it is not in Visual Studio, in Source Control Explorer. Need some help - is there any bug, or I'm doing something wrong..? Thanks
Stackoverflow is mainly handling issues’ open forum while your current question is organization identity/account issue targeting to Azure DevOps, which need assistance of the product group. Thus the best contact channel is here: https://developercommunity2.visualstudio.com/report?entry=problem&space=21, the product support engineer will then contact the product group and offer efficient assistance. Thanks for your understanding.
BTW, you could refer to this doc: Set repository permissions for Git or TFVC to check your account's repository permissions in this project.
I have installed and configured TFS on my server, also I have created a project TEST in TFS. I want to ask how to add code to TFS server and then map it with code in mu local pc.
Any help?
The following should get you started:
https://msdn.microsoft.com/en-us/library/ms181384.aspx
High level overview
Open visual studio
Connect to team collection/team project
Map the team project to a folder on your local pc
Get all the files if any from tfs
Add any files from your local workspace to TFS.
Before you change permission levels for others, make sure that you have the right level of permissions.
Open the administrative context for your team project.
In the Security tab, under users, find your own name, and look at what groups you belong to and what permissions you have
If you aren't a project administrator, you need to be. Find someone who is, and have them add you.
Add user to a team project or a team, etc.
For detailed information you can refer to article below:
https://msdn.microsoft.com/en-us/library/vstudio/bb558971(v=vs.140).aspx
I have a TFS 2010 Work Item Type with a custom field called "Requested By." This field can be populated with any name, but since most of the requests come from project developers throughout the organization, the SUGGESTEDVALUES property should populate the dropdown list with members of any TFS team project.
I have tried various values for SUGGESTEDVALUES, but both Collection\ Project Collection Valid Users and Server\ Team Foundation Valid Users seem to return every valid Active Directory account—well over 10,000 names.
I recognize that one option is to add an ALLOWEDVALUES item with multiple LISTITEM entries for Project\ Contributors for every team project, but with more than 150 team projects in the organization, this would be time-consuming initially and challenging to manage in the future.
Is there any easy way to populate the drop-down with TFS valid users who have actually been assigned to any team project in the collection, and exclude "Valid" users who exist in Active Directory but have never been assigned to a project?
What do you get if you use Project Collection Valid Users?
Project Collection Valid Users is the correct group to use, and I have entered it correctly.
However, one project team wanted to make their code available to the entire organization, and added ORG\Domain Users to the [Project]\Readers group. This was discovered by running a full audit with TFS Projects based on a hunch that something like that must have happened.
Having answered this question with "because a project team was doin' it wrong," I have posted a follow-up question to find out how to correctly grant all valid TFS users access to a specific project. See How can I grant Team Project access to all Project Collection Users? for the discussion on (hopefully) doing this "the right way."
For some reason our developers can only add projects that they've created to Team Explorer, even though they've all been given rights to the other projects. I created a top level group and added all of their AD users to it, and I assigned that group rights to access all of our projects.
They can see the projects in Source Control Explorer, and are able to do their work, but if they try to add a project to Team Explorer, the Connect to Team Project dialog box only shows their own projects.
Is there some other set of permissions?
If you want to make everyone can see and operate each others project, you need to put your team group into Project Collection Administrators in Collection level
If you don't want everyone have admin right,
you need to tell everyone to put the team group into Readers group in the team project they created.
Actually, I don't think there is a way to create a group in Collection level to access all team projects.
In fact, I think the best solution for you situation should be everyone use the same Team project and put everyone in the Reader group in that team project.
So everyone can create their own project under that team project instead of creating their own team project.
If you still want to let everyone create their own team project,
I suggest you use Team Foundation Server Administration Tool to manage group membership.
Permission right usually given on team project level basic. By "top level group" if you mean by giving permission at collection level. then i will suggest you try adding member at 'team project level' under any required group with necessary permission. if you cant add the member ask the admin of the team project to add separately.
you can directly access the security page through web access by.
[TFS web access url]/[Collection]/[team project]/_admin/_security
Under the "TeamExplorer - Connect" there is an option to "Select Team Projects..." When you click on this a box should pop-up titled "Connect to Team Foundation Server" that has a select dropbox, a "Team Project Collections" panel and a "Team Projects" panel. The latter has a list of projects in the collection and each has a checkbox next to them.
Make sure the projects you are interested in are in the list, and have the box checked. You can use the "Select All" checkbox to turn them all on at once.
HTH
I'm new to Team Foundation Server 2010 and I have a question about permissions.
Is it possible for a project to inherit permissions from a project collection? I want to setup a custom contributor group at the project collection level and add the developers to it. Each time they create a new project I want to inherit the permissions from the project collection. That means I don't have to explicitly add the developers to the project each time they create one.
Maybe there is some other way of doing this and not having to setup a custom contributors group? Any help would be appreciated!
I would recommend setting up some Active Directory Groups along the lines of:
TFS Contributors
TFS Administrators
TFS Project Managers
(You could also do this for specific projects. You get the idea.)
Give these AD groups the permissions you need, and simply add/remove the developers to the AD groups. If you can get the ability to manage the AD group, this will be much simpler that administering through the TFS admin tools.
Hopefully, you'll already have AD groups that fit these needs, saving you the trouble. Maybe a team-wide distribution list, for example?
You can create collection level roles (TFS Groups) and edit your process template to grant permissions to those roles so there are set by default in every new project.