Is there any option to configure TFS backlog tree items I'v marked bellow?
EDIT:
I would like to create target structure that looks like:
Current
Future
Experimental
Other
It sounds like you essentially want to add extra metadata to sprints. Unfortunately this is not currently possible (the only metadata supported today is Name, Start Date, End Date).
What some people have done in the past (prior to the Agile Planning tooling), is introduce a Work Item Type called Sprint, then they can define custom fields against it and surface the data in WI Queries.
I suppose you could define a new WI Type and try to associate it with Iterations, but I wouldn't recommend it.
There is no way you can configure the tree on the left panel but since you are using TFS 2013 (also available in 2012) you can use Tags to mark the backlog items that are Experimental or Other.
Add tags to work items to categorize and filter lists: http://msdn.microsoft.com/en-us/library/dn132606(v=vs.120).aspx
Other option is to add a custom field to work items which is not recommended as its painful when you want to upgrade later on.
Modify or add a custom work item type: http://msdn.microsoft.com/en-us/library/hh409273.aspx
Related
I'm trying to build a query that lists all Features and PBIs under an EPIC but eliminate several of the Features that don't apply to me. I can't seem to find a way.
Assume
I need a query that will result in the following
So basically my desired results would be to remove Features 2 & 6 (and all PBIs under them). Since the Title field seems to be shared across Epics, Features, PBIs, etc, I can't figure out a way to remove a couple of features by their titles. I've also tried to remove them by using a <> ID number.
Your requirement can not be achieved by a Tree query. You could save your query and open it in Excel to filter it as the screenshot below shows:
I am getting started with TFS 2015 and I need to know how to make a query that returns all of the work items for the current iteration for the current team. I have Iteration Path Under #CurrentIteration and Work Item Type = User Story, but I can find a macro similar to #CurrentIteration that would get the current team or team area. How do I filter out the stories for all other teams?
It's not able to do this through a query. You could check the Query macros or variables, use the macros described in the following table to filter your queries based on specific fields. There is not any team area related macro.
Besides, actually as far as I know work items can only be assigned to specific people not groups. However, for a workaround. By assigning a work item to a specific area path you basically assign it to a team. If you use the area path for something else today, you can also use another string field in the work item that specifies the team.
(https://www.visualstudio.com/docs/work/scale/portfolio-management)
So you could use Area Path to do the filter.
This won't directly solve your problem but you can use 'Assigned to' 'In Group' and then use a user group e.g. '[Home]\Team NI'. This will return tickets assigned to the group or group members but assumes the tickets are assigned appropriately (rather than being unassigned). YMMV but I've found it useful at times to get around this limitation. TFS Azure 2019 now also includes #TeamAreas - which is helpful unless you have multiple teams using the same areas.
When are working with various Work Item types (user stories,Tasks, etc) we assign tags to reference the area of work. This makes it easy to filter the Backlogs items view to find any related stories.
I would like to build a query to identify Work Items where the tags have not yet been assigned.
I know this can be achieved using excel and filtering, however I specifically would like to do this using the queries. Is this possible??
Thanks in advance for any assistance.
Firstly, I have to say that it is not possible to create work item query to show work items which don't contain tags. As you see that the Operator for Tags is Contains or Does Not Contain, it is not possible to use these two operators to filter out these non-tagged work items.
Secondly, as you have more than 100 tags, it is not an effective way to use "Does Not Contain" operator to exclude all tagged work items.
So,
How about you adding a 'Null' tag to all non-tagged work items to specify that these work items don't have any tags? With this approach, you can create a work item query with Tags Contains Null to list these non-tagged work items.
If you don't want to take this approach, you need to work with excel just as you mentioned above, or take Dave's advice to work with API.
We want to set the iteration path to a default our tree structure is as follows
Root
v10.1
v10.2
v10.3
So we want it to prefill with the latest (v10.3) on creating each new work item.. and in future when we add v10.4 it would then pre-fill that instead.
Are either the default or dynamic update to new iteration paths possible?
It is not possible to have a rule in your work item to default the iteration path.
That said, in TFS11 iterations are first class citizens: they have dates.
The product now knows what is the current sprint/iteration for a team. If you create a new work item in the context of that team it will default the iteration path with that iteration.
See more on teams in TFS11 at http://msdn.microsoft.com/en-us/library/hh528603(v=vs.110).aspx
Is there a way in TFS in VS2010 to specify that a particular iteration is the current one, and then return that for use in queries similar to the way #Project works? If not is there a way to do sub-queries in TFS work item queries?
Looks like Microsoft listened. #CurrentIteration is being added as a token.
That’s great, of course. When looking to write a query against the current sprint, however, you are in danger of losing sight of unclosed work items in previous sprints. When you reach for #CurrentIteration, you probably just mean “all unfinished work that has been committed to a sprint.” If you filter to a single sprint, you’ll miss any stragglers you failed to close or move forward from previous sprints.
Consider using the following pattern, where “ScrumOfScrums\Release 1.0.0.0″ is your backlog path, and all of your sprint paths are children to that:
Filter for work items under your backlog iteration node, but not equal to the backlog iteration node. That will give you all items committed to a sprint.
This will also catch any items that weren’t closed in your previous sprints. Since the goal is to close every item in a sprint before moving to the next one, this query pattern will generally be better than using #CurrentIteration, unless you're looking to find the closed items in the current iteration.
P.S. While this is an old question, it was my top hit when I searched for info on querying the current iteration in TFS.
I'm afraid that there is not such a macro. I personally just have a few "X in current iteration" team queries and then edit those queries to point to the new iteration path at the start of each iteration.
I am going to try using a standard name for the current iteration such as 'Current'. The queries for this iteration would all reference this name. Once the iteration is completed, I will rename it using a naming convention that includes the date for example and the next iteration would then be created with the name 'Current' (or renamed to this if it already exists). The queries would then return results from the new iteration.
- 2010-49
- Current
- 2010-51
I am not sure whether renaming iterations this way will cause any conflicts or confuse the data warehouse for example but this would save on having to create or modify a heap of queries at the start of each iteration.
I would be very interested to hear feedback on this approach!
Query for Sprint in a date interval as shown here:
Team Project = #Project
And Work Item Type = Sprint
And Start Date <= #Today
And Finish Date >= #Today
I have found that Telerik's free Work Item Manager provides an elegant solution to this problem.
Just define your queries as you usually would but leave out any filters relating to iterations (note that this also applies to areas). There is a treeview pane named 'Area/Iteration Filters' that will add extra, recursive filtering based on the iteration (or area) that you select there.
Note that if the pane is not visible then you can enable it via the View menu.