If I create a work-item in project 1 with id 100 then the next work-item would be 101 if I create another work-item but in project 2. I need work-item id 100 in project 1 and work-item id 100 (or whatever) in project 2. Is that possible?
Can I have work item auto-id numbering separated by project?
For this issue,I think it is impossible to make work items automatically numbered in their respective projects. Currently this is designed like so.
The scope of our work is an organization, sometimes we will need multiple projects to work together, so the id of the work item is applied to the entire organization. If there are workitems with the same id in different projects, then we will be confused when we query work items across projects.
In addition since work item ID is unique identifier which is assigned by system, so we can not custom the work item ID when creating a work item. You can refer to this official document.
The unfortunate answer is: no.
The reason lies in the fact that the work item ID is also used as the single unique identifier to link work across projects in the same project collection (on-premise) or organization (cloud). Hence, the number must be unique in the whole collection.
There have been multiple attempts in the past to separate projects and the identifiers. All have met an untimely end due to the complexity involved and backwards compatibility concerns.
Related
We have agile / devops culture -based teams who have a need to track work that has been planned and prioritized at an expected pace, vs work that came in for immediate handling. Some are bugs, some are tasks, some stories, etc.
We're thinking that adding a custom field is the way to go, with potential values of Maintenance and Enhancement. And of course, the hardest part: What would the field name be?
Is there a better approach? We don't think that a new work item is really it, but we could be convinced otherwise.
Additionally, we've looked at all of the canned fields and don't see an obvious field that fits, but we would prefer to use the built-in fields where it makes sense.
What, if any, is the recommended approach? I'd be very surprised if we're the first with this need.
A custom field doesn't have big difference from predefined field, so you can feel free to create one when no existing predefined fields can meet your needs.
I agree with your thought of adding a custom field. As for the field name, we can simply name it PlanStatus,PlannedOrNot or whatever you like...
You only need:
1.One inherited process based on Agile process template.
2.Edit Bug type and create the field.
Then edit other workItem types who also need this field. (Edit=>Add an existing field=>PlanStatus)
3.Then you can create a bug/epic with PlanStatus field and you can use the newly created field in Query. Besides, you can add a widget in Project OverView=>Dashboard to track the planned/unplanned workitems. (Chart for WorkItems widget or Query Results widget or what...)
If I create a work-item in project 1 with id 100 then the next work-item would be 101 if I create another work-item but in project 2. I need work-item id 100 in project 1 and work-item id 100 (or whatever) in project 2. Is that possible?
Can I have work item auto-id numbering separated by project?
For this issue,I think it is impossible to make work items automatically numbered in their respective projects. Currently this is designed like so.
The scope of our work is an organization, sometimes we will need multiple projects to work together, so the id of the work item is applied to the entire organization. If there are workitems with the same id in different projects, then we will be confused when we query work items across projects.
In addition since work item ID is unique identifier which is assigned by system, so we can not custom the work item ID when creating a work item. You can refer to this official document.
The unfortunate answer is: no.
The reason lies in the fact that the work item ID is also used as the single unique identifier to link work across projects in the same project collection (on-premise) or organization (cloud). Hence, the number must be unique in the whole collection.
There have been multiple attempts in the past to separate projects and the identifiers. All have met an untimely end due to the complexity involved and backwards compatibility concerns.
How do I add an existing work item to a the default board?
I can create work items under the Work Items section and I can also create work items by clicking + New Item in the Boards section.
But how can I add an existing item to that board?
I cannot find a setting, field, option anywhere to do that.
This is an organization Azure DevOps.
Your existing item needs to be "visible" to the board by existing in the appropriate iteration path and area path.
Without breaking out all the organization settings that allow you to detail this stuff, the easy way to know the value you need to use is to create a new item on the board you want, and use the values it gets in iteration path and area path on the existing item.
Illustrations:
Make sure your project has areas and iterations that make sense for you. Typically your project will start out with a root iteration path and three child iteration paths:
Iteration 1
Iteration 2
Iteration 3
Iteration paths are used to handle both backlogs and sprints for teams.
The combination of area path and iteration path allows admins to divide sections of the global backlog among the teams that are doing the work.
Think of the connection like a grid. If the rows are iteration paths, then the areas are the columns that divide that row (or vise versa). Multiple teams can operate on the same row (iteration/backlog), but they will only see the work items that also fall inside their assigned columns (areas).
When you create a team the area can be created for you, or you can assign an area to a team after it is created.
You can also change the backlog iteration for a team.
Now your team has a board and a backlog. Again, for your first team, this is done for you.
You have obviously already created some work items, so you'll need to move them into the right area and iteration to make them show up.
This can also be done in bulk from another team backlog
You can configure the board on what to be displayed.
By default, it's the Backlog items, so you will see the work items from your backlog (according to the sprints).
You can't just add a particular work item to the board.
See more details here.
I have migrated my local TFS project to TFSO. Unfortunately I could not use the OpsHub migration tool because the language of the local instance was German and therefore the work-itemscould not be transferred. I have introduced a lot of references to work-items in source-code. The problem is that now the ids starts with 1, resulting in references from code to work items that are not related.
Is it possible to set the ID in TFSO to a specific number in order to have newly created work-items to start with that number?
No, there isn't any way to changeset or specify the Work Item ID. It is controlled by VSTS.
And the reference link between the changeset and workitem is stored in the workitem. So if the you haven't migrated the work items, don't worry about the incorrect reference for the code and work items.
I'm writing a bug-tracking backend based on MongoDB and I'm facing a problem:
My main collections are:
User: represents a user in the system
Project: represents a project (each contains an array of permitted users - references to User)
Bugs: list of bugs (each contains a reference to the parent project)
On the main page, I would like to display the latest 10 bugs from all projects the current user is part of.
It seems like right now I have to first query for the list of projects the user is part of, then then use this list (with the $in operator) to query for latest 10 bugs which belong to those projects.
I was wondering whether there is a better way to represent my data to make this query simpler or is this the only reasonable solution.
Thanks!