Our team have created new teams under one project. For example we have a project called 2021 and then various teams under this i.e. Q1, Q2, Q3 etc. I have created new teams in 'project settings' --> 'Teams'. But, we would like to be able to customise and have different fields for each team as they may require different information.
I have tried editing the process but cannot seem to do this and cannot seem to make different layouts under the work item types in the process for the project.
Any advice on how we can have separate layouts for different teams under one project would be greatly appreciated. Thanks!!
created new teams
Each project is based on a process that defines the building blocks for tracking work. You can only customize inherited processes. Any changes you make to the inherited process automatically appears in the projects that use that process. They can not apply on a particular team.
You may specify or give an example to describe how you want to different customized fields for the different teams, so that we can see whether there is any workaround.
Related
If I create a new project and select the Agile process, my user stories will be grouped in iterations Eg "MyProject/Iteration 1".
However, If I create the project using Basic process and after the project has been created, changes the process to Agile I can group my user stories by Sprint Eg "MyProject/Sprint 1".
The latter is what I want, however as the process was set to Agile when the project was created (not by me), I'm trying to figure out how to change it to use Sprints as default?
Side note:
I cannot create a new project as I lack privileges
I cannot create a new process as I lack privileges
I cannot change to another process because I've already created a bunch or user stories
Although I can create sprints manually, I want it to be default.
Thank you!
From this document, we can know that iteration and sprints represent the same concept in the agile process.
Define Iteration Paths (aka sprints) and configure team iterations
So if you want to visually use Spirits as the default, you can add a new iteration named Spirit in team configuration, or change the name of the existing iteration to the Spirit style. Then set it as Default iteration. As shown in the following figure:
Because your current project is already Aglie process, the initial display must be MyProject/Iteration 1. If you want to display like MyProject/Sprint 1, you have to modify it later.
There are two ways to change the display: changing the process or manually modifying it.According to your Side note, obviously neither is feasible.
If you really want Spirits as default in agile progress project without any manual modification,you could submit a feature request in our Develop Community site. Our PM and product team will kindly review your suggestion.
There is no way to do this without changing the Process of your project.
I am working as a Product Owner for a development team using scrum, we are using VSTS for our backlog.
So far I have been organizing my backlog using Epics and Features, I am mainly using features.
I use Features both to group work items but also for keeping control of delivering stuff. If I for instance know that I need to deliver a certain functionality a certain day then I create a Feature for that and include the needed work items. I need to do that because I manage many projects simultaneously.
So far, so good.
But now Product Management want to start creating Epics and Features for them to organize work. I can live without the Epics, and it is fine that they create the features and I add work items. But when I start executing I need some way to organize into deliverables.
Any idea how I can do that, basically I need a group like features but in between feature and work item
You can add tags for your and other Epics to distinguish them...
basically I need a group like features but in between feature and work item
Alternatively you can create a new work item type like features. Please see Customize a project using an inherited process for details.
Create an inherited process
Custom the process
Add a new work item type
...
Apply the customized process to your project
UPDATE:
You need to add a new Portfolio backlog level, but in Azure DevOps (VSTS) the new Portfolio backlogs can only be added as the top level, that means the hierarchy should be Deliverable > Epic > Feature > Backlog Item.
So, in this case you can rename them to match your requirements, for example rename Feature to Deliverable, Epic to Feature, Deliverable to Epic...
Please see Customize your backlogs or boards for details.
Our company currently has about 10 active projects and 5 programmers.
My manager wants a weekly update on all open items, just a list of them.
I only need the list for our organization, not across multiple organizations.
I can see all open items assigned to me, but I cannot seem to figure out a way to see all open items across all projects.
Is there a way to do this without having to go to all 10 projects then manually compile this list?
It is looking like we have perhaps set stuff up less than optimally.
Is is perhaps better to use less projects and group work differently?
Joe
Hmmm...reading this:
When to add another project In general, we recommend that you use a single project to support your organization or enterprise. A single
project minimizes the maintenance of administrative tasks and allows
full flexibility to cross-link objects.
from: https://learn.microsoft.com/en-us/vsts/organizations/projects/about-projects?view=vsts&tabs=new-nav
makes me think we may have setup or organization wrong. It would have been great if this was made a bit clearer in the documentation. This is the first I have seen this.
You can use a query and check the "Query across projects" checkbox:
For example, this query give you all the bugs in all projects with state "In Progress":
You can save the query and display the results on the dashboard or export to Excel with this extension.
New to VSTS, but not Git. Our small team has the usual mix of web apps, windows apps, other misc applications/services and we keep our database objects in visual studio sql server projects as well. So there are 15-20 or so different sets of code to deal with. Currently, each would have its own Git repo.
Was reading this post regarding single vs multiple "Team Projects".
Then, I posted this earlier but was specific to backlog items, but I suppose my real question was about the bigger picture regarding the idea of a "team project"
What would be a good structure for a small team with this number of applications. Assuming each application generally is worked on independently, but you might want to build 2 or more of these applications together.
How about one team project. Multiple "teams", one per "application".
Its the terminology that is throwing me off.
Can different teams each use a different repo?
Can each team have a different set of build definitions? eg. dev/prod etc
A team project is a container for a portfolio of related applications. A team project can contain one or more source code repos (Git/TFVC), builds, releases, test cases, work items, etc. All of these entities have ways of defining security around who can view/modify them.
A team is just an organizational structure within a team project. You can use security permissions to limit certain repos, builds (or build folders), etc to a certain team.
The generally accepted guidance is to keep everything in a single team project. There are lots of things that don't cross team project boundaries, such as repos. Work-arounds usually exist, but they are typically awkward.
The one requirement you gave ([we] might want to build 2 or more of these applications together) is actually slightly tricky regardless of whether the repos are in one or in multiple team projects -- a build definition can be hooked up to a single repo. If you need to bring in additional repos, you'll need to use submodules or add an extra build step to clone the second repo. I can almost guarantee it'll be easier if everything is in the same team project, though.
The one-word answer to the two direct questions you asked is "Yes."
How you set up your structure is really depending. There are many ways to organize it. Single repo, multiple repos.
If you are using CI builds, have in mind that the get sources task in your build will download your full repo. So if you have a single repo strategy your build could take longer to run. In this scenario you would also have more work to setup your builds and specify path filters to trigger only the correct build on your CI process.
Can different teams each use a different repo?
Yes they can.
You can create a security group for each team.
Then, on you team you can remove it from Contributos and add your new group as part of Member of:
After that, in your version control settings, add your new security group and remove or deny access to Contributos security group. This way, only your team security group will have access to the repo.
This is optional. You only need to do it if you want to isolate access to your repos.
Can each team have a different set of build definitions? eg. dev/prod
etc
You can setup a build for each of your repos.
If you need to isolate who has access, you can do it by changing the security on each build, removing contributos and adding your security group.
Still new to VSTS. Sometimes work or requests come in and our team needs a way of sorting these into areas that will become projects, but not immediately. Can I create a task without first creating a new team project?
Also, is there a way to see different projects at a higher level than the tasks in one view on a kanban board? Ive seen some delp docs on dashboards etc, but everything including tasks are all scoped to a team project. While this makes sense to have these things for a project, but what about higher level views? At any one time, there might be 4-5 different projects being worked on as well as 2-3 different things that are not part of a project yet. Maybe VSTS isnt the place for these more general items, but a generic kanban board?
The term "team project" is kind of an antiquated name that doesn't do a great job of accurately describing its purpose. Think of a "team project" as a portfolio of related applications rather than something for a single team, or a single project.
The most common way to address is this to keep everything in a single team project. There are a lot of things that don't cross team project boundaries, and trying to force that behavior is a recipe for frustration.
Within a team project, you can create Teams. Each team can have its own backlog, its own iteration schedule, etc. Teams are assigned an area path that they own. If a work item is under their area, it's assigned to that Team.
If you have Team A's area path set to FooProject/Team A, then it belongs to that team. A work item under FooProject/Team A shows up on that Team's backlog.
From there, you can adjust security permissions and such so that if a person isn't a member of a given Team, they don't have access to see or manipulate other teams' work items.