What would be the query to get list of all bugs linked to particular workitem in TFS 2012?
or any other way to get list?
The process template is MSF for Agile Software Development v6.0.
Thanks!
Here is an example for looking for work items that have a bug linked to them:
Make sure you change the query type to work Items and Direct Links. You can filter down either the main query, or for the linked work items.
Related
I'm working on a large software project that uses TFS for Backlog management. We're using the Scrum 2.2 template in TFS 2012. Are there any tools out there that will give diffs of particular fields (e.g. Description, Acceptance Criteria) so that I can see how these fields have changed over time and who made them ? Sort of like the 'Annotate' feature in the Source Control explorer, but for Backlog Items instead ?
You can create your own tool to highlight differences between revisions of a specific work item field with TFS API. You need to work with WorkItem.Revisions property.
There is one tool available with which you can have a reference to get started quickly, see: http://gethistory.codeplex.com/
Im trying to create a custom TFS wit with a custom wit that is referenced to my changesets IDs.
For example, I need a field that contains a list of changesets IDs from my existing changesets in the TFS project.
Is it possible for making and customizing such field?
Thanks!
Yes, it is possible. You need to work with a custom work item control.
In the work item control, you can get a list of changesets via using TFS API (use the VersionControlServer.QueryHistory method). Also check this stackoverflow case for the details: TFS 2010: Getting list of changeset Ids
Please have a check on this link for the detailed information on how to create custom work item control: https://witcustomcontrols.codeplex.com/
I just received instructions to add the TFS element number to the comment of any changeset I commit. I find this mesure redundant because I already have to assign the TFS element to my changeset.
I was told it was because it was hard to obtain the list of TFS element a developper worked on.
Isn't there a smarter way to obtain this information?
With using Work Item links between a Changeset and Work Items (the recommended approach - assuming your are using TFVC), you could write a bit of code against the TFS API, or a query against the TFS Data Warehouse to retrieve all changesets by Developer A, then traverse the WI links to find all WI's.
After using the 'Search Work Items' plugin for TFS 2010, I am struggling with the seeming limitations of the similar tool in TFS 2012.
My teams use this ad-hoc query to quickly search across all team projects to find work items based on a number of fields. I have been unable to find a way to modify the query to search additional fields and remove the #Project limitation. In TFS 2010 using the "--Template" string to open and modify the query was the ticket. Is there a similar solution in TFS 2012?
It is possible to manually specify all the extra fields every time using the search syntax (painful) - but how to remove limitations such as #Project etc?
You should just be able to open a query in Team Explorer and remove the #project designation. You however will not be able to remove the #project limitation from the search box now on the TFS 2012 Web Access UI as it will only search across a single Team Project.
I would recommend that you read:
http://blog.hinshelwood.com/project-of-projects-with-team-foundation-server-2010/
http://blog.hinshelwood.com/one-team-project/
I think as you go forward you will find more and more that you are running into the Team Project boundary.
I am using TFS 2010.
I have many work items (requirements, test cases...)
The work items are linked. I know how to do a query to see the hierarchy of the work items, but when I want to export them to Excel I have just the option to do a flat report.
How can I export a Hierarchy report of work items?
You can only export a flat list or the Tree of Work Item (for the parent/child relation) to Excel.
If you feel that it is important to have this feature included in a future version, you can use User Voice to add the suggestion. We, as the TFS product team, take these suggestions seriously (and of course the more votes the more likely it will end up in a future version)