This is in Team Explorer 2010
Question:
Using WIQL, is it possible to get the list of file differences due to checkins
for a given date range
for a given folder
WIQL is about work items alone - so it isn't possible to retrieve this kind of information through this path.
Using the TFS data warehouse should provide with a viable alternative. A very nice introductory presentation can be found here.
You should probably make a focus on the filters "Version Control Changeset" in combination with "Date" filter for your (1) & "Version Control File" for your (2).
Related
I need to add tag reporting capability to a collection of custom SSRS reports which query TFS_Warehouse (and in one case I had to query the operational store to gather test case steps). These reports all use a SQL Server datasource connected to my custom TFS_Warehouse_Extensions database.
If this sounds familiar, I asked this question yesterday and got a wonderful response... then I discovered we upgraded from 2013 to 2015 last week and dbo.workitemsare is gone.
I am using VS 2015 and am more of a database developer than a C# programmer (I know just enough to be dangerous). Is there any way I can get tags from TFS 2015 workitems into my SSRS reports?
Edit: the proposed duplicate answer is not exactly the same problem. Whether or not some work items views went missing is ancillary. My requirement is for a way to query TFS tags in SSRS. So far I consider this unanswered in either thread since no one has proposed a solution that meets the requirement.
#Cyndi, I'm a Program Manager with the reporting team. Currently reporting with Tags is not supported aside from queries with the query editor. We do have a new reporting solution we're working on and reporting on tags will be supported. I don't have an exact date for the release yet, but see this blog post for some details. We'll have more announcements to make this summer.
One totally diffrent way would be to use Excel for reporting.
You build a query in TFS and then connect Excel to TFS and use the query. The functionality is kind of limited, but you can use Excels features to make great reports.
One problem with Excel is that you can't (you shouldn't) add further fields to the table you got from TFS. When you update the data, Excel will lock up and nothing happens.
If you need to use custom fields for your reporting, you should create a second table, where all the data is copied to. This can be as well automated with VBA.
That data can be analysed directly in the table or with a Pivot Table or visualised a Pivot Chart.
With the use of the Pivot feature Excel is able to create powerful reports.
It's not a good idea to query the operational store. This may cause some problems for normal usage.
You should NEVER write reports directly against the WorkItem* tables
in the collection database, since this is an operational store and is
100% unsupported and can cause performance problems for normal usage.
Source: How to query Work Items using SQL on the Relational Warehouse
We can search for work items under an iteration per project, but we'd like to search in ALL of our projects, if possible.
The My/Team query builder won't let you use a wildcard in the Iteration Path, which means you must select a specific iteration in the Iteration Path 'Value' dropdown...
I figure we may be able to run a SQL query on the backend, but there is red tape involved in that solution...are there any other solutions?
As to the 'why' question: we would like to track all open 'hotfix' work for all of the projects. Aside from having someone enter the term hotfix into the title of a work item (which introduces human error, but would be searchable), we're not quite sure how to do this by searching for iteration.
No, there is no way to do this without a great number of "or".
You should consider merging the team projects that you are encountering this issue with. In addition you should upgrade TFS to take advantage of the new team entity for splitting up the work.
http://nakedalm.com/one-team-project/
I need to build query, that return result with network topology with more than 2 level in depth. For example, i wont to get next result:
but if i build "Work Items and Direct Links" query i get only 1 level depth, and if i build "Tree of Work Items" i can select onl Parent/Child type of tree and can't add my custom Successor/Predecessor type of tree.
So my direct question: may i get more then one level depth in Work Items and Direct Links Query, or change type of tree in "Tree of Work Items" Query? Or i can get that result only by integrating TFS with Project Server like this?
There are two ways to do what you are talking about and it depends if you want to create reporting or if you are talking about a work breakdown structure.
If you require a work breakdown structure I would recommend changing your process so that you do not, or processing that purely at the PMO level. Enshrining dependencies in a tool at anything lower than the Portfolio suggests to me that you may be creating solutions to effects rather than getting to the route cause of a particulate dysfunction that is enshrined in your culture.[preachMode=false] However...
#1 - Reporting
You can create a reporting services report that presents data from both the Data Warehouse and the Cube to create the desired view.
Create and Manage Reporting Services Reports for Visual Studio ALM
This will give you a read-only view of data and will lead to the least invasive dysfunctions.
#2 - MS Project
You can use MS Project to load both the Parent/Child & Network items and maintain the Gant Chart with dependencies that are stored in TFS.
I could not find a good link but there is documentation on MSDN
This will give you an interactive view of the data in the operational store, but will lead to the most invasive dysfunctions.
#3 - Project Server
If you are implementing something more like the Scaled Agile Framework then you may want to take advantage of the Earned Value management of Project Server integration as well as some of the Portfolio Management features.
Enable Data Flow Between Team Foundation Server and Microsoft Project Server
I hope that you can find something to suit and you get a chance to explore the ramification of your current process on the ability of your teams and organisation to achieve any sort of agility in the new normal of the modern application lifecycle.
We are currently trying to find a new bug tracking and integration software and we were looking at FogBugz, Jira and TFS. My question is about TFS.
I have done some research and found that TFS has "Power Tools" in which Non IT users can log on and get some information, but all the examples and tools I have found didnt really give them the kind of UI that other bug tracking software provides such as estimates, full fledged reporting on hours, P&L, Bugs Released, When A feature will be complete. For example Fogbugz has a feature that will predict when a feature will go live off past estimates, is there any way to get that kind of functionality from TFS? Or Any of the functionality listed above in a web interface?
Team Web Access is built into TFS 2010 (grab a trial and try)
Urban Turtle is the best Web UI for dealing with Work Items in TFS.
Reporting and Bug reports are available, though everyone, everywhere wants something different.
P&L reports are not available out of the box.
There are minimal prediction reports, but it's all BS anyways :). Burndown reports give you information about your likelihood to delivery.
As you mention, there is a tool called Team System Web Access Power Tool with following features:
* Direct links to work items, query results, diffs, change sets and more
* Display custom controls on work item forms
* View queued builds new, queue new builds
* Add new work items or edit existing ones
* Work with any type of work item, including custom ones
* Add new work item queries or edit existing ones
* View, download, upload, check-in and check-out documents on SharePoint team portal
* View reports, export as PDF or Excel
* Browse source control repositories, download files, view changesets, diffs, histories, and annotated views
* View build results, start or stop builds
* Search for keywords in work items
If you need more than that you'll have to integrate the TFS with SharePoint server which will give you all you asked for in your question and much more...
We are using VS 2010 and TFS 2010 with the Microsoft Scrum Template.
We use the Team Queries for the Current Sprint like the Sprint Backlog query.
The problem is when we move to sprint 2 the "Current Sprint" still points to sprint 1.
Is there a way to to tell TFS that we are now currently in sprint 2 and have the queries use a variable to run against instead of hard-coding the sprint?
For example: If you look at the screen shot below you will notice that the definition of the query uses a variable called "#Project" for the team project. Is there a way to have a variable for the sprint?
Tom,
What you are asking for is not available in TFS 2010. There are not even dates on the iterations, so TFS does not know what the current iteration is.
In TFS11 (vNext) we have added the dates on the iterations. It now knows in which iteration you are, and this is also reflected on the backlog page in web access. In the preview version that is out now it is however not possible to add a filter clause to your queries to filter on the current iteration (something like #CurrentIteration). We have heard strong feedback to add this in the product before it ships. It is also very high on our wish list, but we need to fix other things first before we can ship.
You can add this request on User Voice. If the idea gets lots of votes it makes it easier to build a case that we need to put this in. But we cannot promise anything.
Ewald - TFS Program Manager
Almost all answers here say that you either need to wait until Visual Studio implements #CurrentSprint token or to change all existing queries manually.
I found another great practice that might help you which is explained here:
http://intellitect.com/transitioning-between-sprintsiterations-with-tfs.
Try to create a “release” called “Current” and move the specific current sprint under it. It's much easier and quicker than dealing with queries every time you start a new sprint.
You could modify the work item query programmatically: http://www.ewaldhofman.nl/post/2010/03/09/TFS-SDK-2010-e28093-Part-6-e28093-Replace-text-in-all-Work-Item-Query-Definitions.aspx
I've only ever read documentation/guidance (links unavailable at the moment), that said at the start of a new sprint there are a few various steps you need to take in TFS, e.g:
create the new sprint/release nodes
set the applicable PBI work items' iteration to the current sprint
set the applicable PBI work items as committed
update all the "Current Sprint" queries to reflect the new sprint number.
I've never seen documentation on doing the last step list (or any of them) in a hands-off (automatic) way. That said, I'm not suggesting it's not possible, just stating that I've never seen guidance on how to do it, but have seen plenty of guidance on doing it manually.
You could use a plugin called TEK workitem. TEK workitem is a Visual Studio extension for TFS that allows bulk edit of query definitions, besides other features like open in Visual Studio workitems and queries from a Hyperlink, delete Workitems from Visual Studio UI, etc.
You can download a demo from Visual Studio Gallery: TEK workitem
I am pretty recent to TFS Scrum 1.0 but this is what I do.....
I am currently managing my sprint dates outside of the template
I use the 'Current Sprint > Query’s' to give myself and team quick access to the queries on the current sprint.
When I finish a sprint and want to increment to the next sprint and have the queries under 'Current Sprint' point correctly I do the following:
Edit each query under ‘Current Sprint’
Right lick and select ‘edit query’
You may see an error dialog if you have changed the hierocracy of your iterations. OK to click through to the query editor.
Set the value of ‘Iteration Path > Under’ by selecting the correct sprint from the drop down (populated with your iterations.
Save the query and bob’s your anty…. Queries will display you current sprint. Just repeat each iterations.
Hope this helps....
I found in TFS 2013 that if you uncheck the sprint/iteration the one with the earliest dates get assigned to current automatically. If you want to keep the old one visible, move the dates out a year or so and it drops to bottom of list, but out of scope.
This is TFS online 2017
Step 1) Settings-> Work->Default team settings
Step 2) and then 'Default Iteration'->Change
Keep in mind that next time you might be starting in Step 2. So Step 1 is optional.