Using Team Foundation Server 2010 with the Scrum for Team System v3 template, I'm not able to view calculated fields (specifically the Work Remaining field) in Project 2010. If I export my Project Backlog Items into Project, the "Remaining Work" value shows up for each Sprint Backlog Task (since it's not a calculated field), but doesn't roll-up for the PBI. Does anyone know how to make this work? Is there a field mapping I'm missing?
Yes, turns out there was a field mapping I was missing. I mapped the Scrum.v3.WorkRemaining field to a custom Number field in Project, and I was then able to add that column to my Project plan!
Related
I need to set a default value for the Retrospective tab in TFS 2015.
Factory value is the following (TEXT 1):
What worked?
What didn't work?
What will we do differently?
Using the Powertools, I add a DEFAULT rule. In the rule i specify the following default value for the Retrospective (TEXT 2):
What worked?
Please check out what you wanted to do differently in the last two sprints.
What didn't work?
What will we do differently?
So really it's just adding Please check out what you wanted to do differently in the last two sprints.
Now here comes the problem. I save my work, and if I create a sprint in Visual Studio, TEXT 2 is displayed.
If I create a Sprint in Online TFS (accessed from browser), it will show TEXT 1.
Did anyone have a similar problem in the past?
Thank You in advance!
The Sprint work item, used in TFS 2010 with the MS Scrum 1.0 process template, was removed from the Scrum process template 2.0 of TFS 2012.
However since TFS 2012, you configure the sprint schedule as part of the new Agile Planning feature, making the Sprint work item redundant.
So your options for storing the goals\retrospective:
Use a Task work item (Title, Description fields)
Add custom field in the Product Backlog Item
Use SharePoint integration - store as a document
Is it possible to reset the work item type history that is proposed to a user who creates a new WorkItem query?
We have some TeamProjects that went through two Process-Template customizations including localization and WorkItem form layout optimizations.
With TFS 2015 we're finally moving to the Agile process template. The problem is that somewhere the TFS stores the WorkItem-Types you have ever used and displays them in the WorkItem query designer.
The values in the Work Item Type are mixed both german and english and are picked from all of the past process templates the team project has ever been configured to use.
Is it possible to reset that list and if so, how?
The scope of the query editor is for all projects in a give collection. When you open the dropdowns, it thus shows all work item types in any of the projects in the collection.
In TFS 2015 we have added a checkbox to scope your query to the existing project. This checkbox is off by default because the majority of the queries run in the scope of a project. When the checkbox is unchecked, the dropdowns are limited to show only the states, fields and work item types that are in use by the existing project.
If you don't need these work item types and the work items, you can use witadmin destroywitd to destroys the work item types, after running the destroy command, the work item types will disappear from the drop-down. But please notice this will also destroy every work item of that type permanently without recovery.
witadmin destroywitd /collection:CollectionURL /p:Project /n:TypeName [/noprompt]
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/
I'm working with TFS 2010 and Project 2010 Feature Integration pack and the Scrum for Team System v3 process template. Within the Project Server tab, I'm trying to set the default value for "Submit to Project Server" and "Enterprise Project" (which works fine), but when the Project Backlog Item is created/saved, it always fails when trying to sync with Project Server with the error message in the title of this post: TF285017: The Assigned To field cannot be blank.
I've Googled the error code, and it seems like there is no documentation for it anywhere. Can someone help?
Ultimately I fixed by adding the Assigned To field to the template and making it required. This probably isn't the best way to solve this issue, but does get around the error (and making the field required was something I was going to do anyway).
As the error states, in the TFS process template for the backlog item, the Assigned To field is mandatory. It needs to be filled before it can be synced with the other system.
You might try to remove the required flag from the Assigned To field in the workitem by using the TFS Power Tools process editor.
I'm trying to add 3 fields to some Work Item templates in my TFS 2010 project so we can do simple release notes documents generated via reporting services.
Using the Process Editor (in TFS Power Tools Sep 2010) I have added 3 fields, all String types - "Version", "Title" and "Description". Each has had the Reportable attribute set to "Detail". I used String since it seemed only that type was reportable.
This works well and I have produced a report that shows simple release notes that I enter in Work Items.
The trouble is with my Description field. It seems the string field can be no longer than 256 characters and if I try and enter more when editing an item I get an error.
I initially considered using a field type of (ideally) HTML or PlainText but the process editor warns me it's not reportable.
So, finally my question - is there a way of increasing the length of a string field in TFS 2010?
Thanks,
Chris.
You're going to be stuck with the 256 character limit for reportable fields. However, understand what "reportable" means-- it means that it won't be replicated to the TfsWarehouse database or to the OLAP cube. You'll still be able to access it through queries within TFS / TFS Web Access, as well as through Excel integration. Most of your reporting needs may be able to be satisfied through these means.