I ran into some problems that I blogged on in my TeamPlain - Install and initial views post. I have got a work around for the long project name problem, but it only works when you really daft project names like ours:
“XXEMEA-UK-Area-Dept-BusinessUnit-[Project Name]”
What I have done is rewrite this drop down list after it has been rendered using JavaScript!
Eww, I hear you say. Well as team server does not support compartmentalization of projects out of the box the long project names must stay.
Here is the code:
Put it after the drop down list by the id of “cmbProjects” and change the remove function calls for whatever you need.
I know it is ugly, but it is the sort of “Tactical” work around that gets the short term problem sorted.
I permanent solution would be nested projects (Or and Organizational Unit separator for the project name) from Microsoft, but I don’t think it is on the cards in the near future!
Technorati Tags: ALM
What to read next
Branch madness!
Describes a complex source control issue in TFS involving branch mismanagement, its impact on merging, and step-by-step actions taken to …
TFS for cross team and cross business line work item tracking
Explains how to use a single Team Project and Team Field in TFS to streamline cross-team work item tracking, reporting, and collaboration …
Solution to sub sites in Sharepoint 3.0 with Team Foundation Server
Explains how to configure Team Foundation Server to create SharePoint 3.0 project portals as sub-sites, including manual and automated setup …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …