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
Related
We are using Azure DevOps for development. We have several teams but one team needs to be the "Default" team. Does this affect anything else than that the default team can not be removed? I have not found any documentation what the project default team does.
https://learn.microsoft.com/en-us/azure/devops/organizations/settings/add-teams?view=azure-devops&tabs=preview-page
https://learn.microsoft.com/en-us/azure/devops/organizations/settings/about-teams-and-settings?view=azure-devops#the-default-team
In the docs you sent:
Backlogs, boards, and dashboards are automatically configured for this
default team so that you can start defining work items and your
backlog.
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.
If a ticket is assigned to a defined team board in Azure DevOps, is there any way to make it visible on the default team board as well?
So if I have a default team called Oversight and a team board for the analysis team and assign a ticket to them, I want this to appear in the default team board (oversight) as well.
I cannot see a way to do this.
Basically I want the team to manage their own board but for the PM and Scrum master to have oversight of all items assigned to the team and being worked on. It would be a bonus if the item progressed through the columns \ states it moved on the default team board as well.
If a ticket is assigned to a defined team board in Azure DevOps, is there any way to make it visible on the default team board as well?
By reference to this doc: Start using your Kanban board, each Kanban board is associated with a team and a work item type. Thus currently it is not supported in Azure DevOps to view the same assigned work item in 2 different teams’ boards.
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. Appreciate for providing valuable feedback to help improve the product.
BTW, you could add the default Oversight team to be member of the analysis team, and then member of this default team can switch to the analysis team board to view the work items. See: Open your Kanban board from the web portal for more details.
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.
We are a small company and are still unsure how to start all this azure stuff.
Ok, we are clear on the technicalities like table storage and queues and all the that stuff, what we don't know about at all is how to set up the organization around developing for our developers. Which/how many azure accounts, shared or individual ones.
So far we've done classic windows development, so everyone has his environment, unit tests run either locally or on the build server (after pushing to mercurial or git), deployment from the build server.
The thing is that we want to use Azure not just as a hoster, but the full set, like blob/document/table storage, event hubs, storage queues, ReliableActors and everything. Things we can't do locally.
What's the appropriate way for azure then? There are about 20 to 30 developers and most have the enterprise msdn subscription.
What is a "company or organisation" account for? Should developers have their own accounts? Does DevOps need their passwords for all the bamboo or jenkins build stuff?
I went through this recently and I can share a few tips here since I'm also not aware of a DevOps specific platform to share this on StackExhange.
As far as organizing your subscriptions go look at Azure Pay-As-You-Go Dev/Test Subscriptions link
or Enterprise Dev/Test link if you are an Enterprise Agreement customer. These are aimed at development teams, you get discounted rates since you don't pay for software licenses that are already included in your MSDN subscription.
It is best to use individual developer subscriptions for exploration, POC etc while running your main dev workload in the Dev-Test subscription. It looks tempting to try and save a buck by spreading the work across multiple MSDN subscriptions to use the credits but I wouldn't recommend it. It becomes a pain to manage 20~30 subscriptions and they can run out of credits and things stop working. If you remove the spending limit on all the subscriptions you run the risk of racking up a huge bill accidently if multiple devs leave VMs on or add premium storage to VMs etc.
As far as DevOps go, use RBAC and Azure Active Directory to manage access and certificates for your DevOps tooling, build servers, release management etc don't use individual developer credentials for this.
And I agree with the other comments, get in touch with MS as well, this is just the tip of the iceberg but it will get you started.