In Azure DevOps, a default project team will be created when we create a new project in a given collection. We can then add/invite members to this team and assign their level of permission. So far it is clear to me.
However, in my case, I have multiple projects and in each project there shall mostly be static set of developers.
Question:
a) Is it possible to create a default team at collection level (rather than project level) and assign users to it?
b) If srl (a) is possible, how would we instruct Azure DevOps to assign this default team as project team for all projects those shall be created under project collection ?
For example: Within a collection called Services, I have projects with users like below
Service A will have developers x, y
Service B will have developers x, y
Service C will have developers x, y, z
I prefer a default team with users (x, y); and this team will be assigned to all projects those are created under Services collection.
Exception: Service C has an extra developer Z. This is fine since we can visit project and explicitly add this developer.
a) Is it possible to create a default team at collection level (rather
than project level) and assign users to it?
No, it's impossible. In Azure DevOps, we provide collection-project-team structure.
Within a project, you can add teams
You could take a look at our official doc here-- About projects and scaling your organization and then decide if you need to create multiple projects or teams in your scenario.
As the above doc mentioned, we would suggest you handle a single project. Can a user account belong to more than one team?
Yes. When you add user accounts to a project, you can add them as members of the project, or you can add them to one or more teams added to the project.
Besides, you are also be able to structure hierarchical teams. Although there's no concept of subteams, you can create teams whose area paths are under another team, which effectively creates a hierarchy of teams. To learn more, see Add another team.
afaik it is not possible to create teams on collection level. you could, for example, create an Active Directory Group and use/reuse it in your projects.
Related
I am setting up some simple Azure services for a company that does not have an IT team yet. My three goals are
The company has to use the Azure portal minimally. The owner is not tech-oriented.
The company can add billing information for the subscription themselves without having to give me all that information.
I can eventually transfer ownership of the azure entity (directory? tenant?) to an IT team.
I cannot find the answer online because all the documentation is oriented towards an IT that works for the company as opposed to freelancer. I am currently using my personal Microsoft account but am able to get a company Microsoft account if needed via their parent organization (which does have IT). Using my personal account, I've created a new tenant then switched to that directory. In that directory I've attempted to add a subscription but it switches me back to my default directory. If I switch to the new directory again, I get the error "In order to view your eligible offers, please click here to switch your directory to {my account}.onmicrosoft.com"
I would appreciate an in-depth answer as I am not familiar with the administration side of Azure.
I'm a member of one of my colleague's personal Azure DevOps Services organization (I hope I'm using that term correctly). And there's another Azure DevOps organization that we're both a part of. In my colleague's personal organization there's a project I've been working on for a while. My colleague and I both agree that it would be best, at this time, to move that project from his personal organization to our company's organization in Azure DevOps Services. Only, we don't know how to do that.
So, is it possible to move a project (code, wiki, board, etc.) from one Azure DevOps organization to another? If so, how do I go about doing that?
Daniel Mann's answered my question in his comment in reply to my question:
No, it's not possible to move a project between organizations. The
best you can do is employ various migration tools to recreate the work
item data in the new organization, and accept that there is going to
be some degree of loss of fidelity. For example, you can easily move
your repos, but pull requests are simply not transferrable.
I am creating an azure custom vision project in python, every time i run the code, it creates new projects and my project count keeps increasing.
How can i delete an existing project before creating a new one?
First you're going to want to check which projects you have, which you can check with the GetProjects API. This will give you have a list of projects with their project ids. Once you have project ids for the projects you want to delete, then you can just call the DeleteProject API, passing in the project id. You can also managed you projects via the Custom Vision Service portal at www.customvision.ai, just be sure to sign in with your account.
I have two Projects in one Organization (like in the attached image below).
I would like to see the items from both Projects in the same Azure DevOps Board (dashboard).
Azure DevOps Boards (dashboards) show just the items from the selected Project.
How can I add items (User Stories) from both Projects to the same Azure DevOps Board?
(There is pretty good documentation on https://learn.microsoft.com/en-us/azure/devops/boards/?view=azure-devops but I did not find the answer)
How I can add multiple projects on the same Azure DevOps Board?
Just as we know, Azure DevOps Board is associated with an Iteration Path(Agile). An iteration path only exists within the context of a Team Project. So, Azure DevOps Board boards by their current implementation live only within a Team Project.
As a workaround, you can try to use the extension Delivery Plans, with Delivery Plans, you gain tailor-made views across several teams and their development backlogs—stories, features, or epics. You can use these views to drive alignment across teams by overlaying several backlogs onto your delivery schedule:
Check the document Managing project schedules across teams with Delivery Plans for some more details.
BTW, there is a user voice Single Dashboard for Multiple Projects, which is on the roadmap, you can vote and track the feedback from this ticket.
Hope this helps.
You cannot do that. I think you have to use one team project and several teams. Just create separate teams for each project. Azure DevOps will create an area path for each team. Then each team will use their own backlogs. In the default project team you can select "Include sub areas," and then you will see items for all teams (or projects).
Additional links:
Add a team, move from one default team to several teams
Define area paths and assign to a team
I'm using Gitlab 5.0 to manage my git repositories and I've never used github before Gitlab.
When I create a group, I see a new directory with this group name in /home/git/repositories.
But with team, no such thing is done.
Also, with group, I can create a project for the group and the assignments (for users of this group) is done automatically.
I can't see any other differences between group and team and I would like to understand that.
Thank you in advance and sorry for the bad English (I'm french),
GitLab 6.0 (August 2013, 22d)
See commit 3bc4845:
Feature: Replace teams with group membership
We introduce group membership in 6.0 as a replacement for teams.
The old combination of groups and teams was confusing for a lot of people.
And when the members of a team where changed, this wasn't reflected in the project permissions.
In GitLab 6.0 you will be able to add members to a group with a permission level for each member.
These group members will have access to the projects in that group.
Any changes to group members will immediately be reflected in the project permissions.
You can even have multiple owners for a group, greatly simplifying administration.
Why do references to Teams still exist in GitLab 7 then? e.g. "Filter by Team"
"Team" seems now (GitLab 6.x->7.x 2015) seems limited to a project (see for example features/project/team_management.feature, and app/models/project_team.rb or spec/models/project_team_spec.rb).
A project can be part of a group: see "Gitlab API for all projects under group".
"Group" references users, and can group multiple projects, (See features/groups.feature, app/models/group.rb, app/models/members/group_member.rb)
As a user, you are a first a member of a group, and have roles ('Reporter', 'Developer', ...) associated to a project (which makes you a member of that project, part of the "team" for that project).
No role, means "not a member of the team for a project".
See db/migrate/20140914145549_migrate_to_new_members_model.rb.
Answer for GitLab 5.x (before August 2013, 22d)
Group is for grouping projects, similar to a folder (git repositories)
Team is for grouping resources (people)
Those notions have been refined in GitLab 4.2.
That allows you to manage authorization in a more convenient way, given permissions to a group of projects in one operation, and/or given permission to a group of people, referenced by their team.
GitLab 5.x no longer used Gitolite, but before 5.0, teams and groups are coming from Gitolite, and its gitolite.conf configuration file.
This is where team and groups were declared and associated in order to grant permission access.
Even without gitolite, the idea persists: managing the authorization through association between teams (of people) and groups (of projects).