rename project in TFS
Rename existing project in TFS
We’re taking another look based on all the feedback here! As Doug pointed out, this is rather hard problem though.
- Siddharth (PM on TFS)
We need to be able to do this. This functionality can and should be implemented.
Stunning that this cannot be done!
It looks like this is coming soon! http://blog.thoughtstuff.co.uk/2014/05/tfs-project-rename-is-coming/
We are actively moving off of similarly limited legacy technologies. The business value is outweighed by the increasing support costs. This fits given we use the basics features of version control, bug and issue tracking, builds and simple agile planning. The largest cost in our 50+ person software project dev, QA, UX, management team is people time; and that people time cost is very minimally changed by using anything beyond the basic version control, bug issue tracking, build and agile planning tools. An added benefit of this simplistic approach is that each group needs to build a significant business case for adding any custom scripts or code to any of the code in the check-in, build and package pipeline.
Steve Forth commented
In my case our product name has been changed after we created the initial TFS project. The TFS project now refers to the old Product name. This is quite confusing for a bunch of reasons. We don't want the whole copy and start again approach as we have a large backlog defined and really do want to keep the history.
We are using TFS on-line i.e. at VisualStudio.com.
I don't mind if the underlying project name never changes so long as I can have the project name displayed as the new name and the URL to read the new project name. What I'm trying to say is that a display alias would work for me.
Paul Katz commented
Yes, renaming capability would be highly, highly valuable
YES for Michael Cowan's feature as described in his March 12th, 2014 post!
I need to rename a project. Our client who has view access to TFS wants to change the name. The name is also easily confused with another project, and sometimes work items are entered under the wrong project. We need a fix. As a workaround, I have a number or queries and activities I do to ensure all the items are in the right place. This takes hours every sprint.
We have a little joke to make light of the occasional lacking TFS feature (can't query tags, cannot easily remove weekends from the burndown chart, new work items default to current sprint). We say "WTFS!"
It is to know another team pushes some doozies to production, not just mine! Overall, we love TFS.
As you look at how to solve this I'd recommend going back historically and seeing if anyone has notes from when the problem of how to move from the DOS 8.3 file name standard to Windows long file names was successfully tackled, since that's somewhat similar, in that the impact of getting it wrong would've been huge, but they found a way through it by having every filename have a unique 8.3 equivalent being managed (as I understand it). I also think the idea mentioned by Michael Cowan below is on point. That is, you take the existing infrastructure and add one or more properties to it (DisplayName). The existing identifier goes through the arc that 8.3 filenames went through, that is, right now it's overt, but eventually it could fade more in the background as an internal property.
Nate - how do you clone the existing project and not lose all the work item meta-data (links, IDs, attachments), test asset meta-data(test suites/test plans), lab management meta-data (builds/build results), version control meta-data (annotations, history, labels), and security meta-data (groups, permissions)?
If you have some solution that gives you all that meta data under a new name.....please share your workaround.
Just clone a existing project and then delete the old one.
Michael Cowan commented
I have a great idea to mitigate this.
Add a new property called "DisaplyName" to the project. If its blank, use the original name, if its not blank use that name everywhere.
Also create a GUID ID for each project that can be used instead of any name. So all scripting / API can be done against the project GUID.
Keep the initial name plumbed everywhere as you have it. Let all API's continue to use the original name .. but allow us to use the GUID ID and friendly display name.
Yes, please please please
I vote for this feature, too. It's a must have!
Jab Jab commented
Please get this done soon!
Doug Baker commented
This would be very valuable when restructuring team collections and consolidating team projects. I could be making good use of it right now if it were available.
Daymon Nin commented
I want this too
Johan Meijer commented
It's unbelievable that this was not a must when developing the first version of TFS. As a software developer, the first thing after creating a functionality to create an item (ANY item) is programming a way to edit that item. What if I made a typo, what if the project changed over time, so that the name doesn't serve it's purpose anymore? And yes I know, I can use some third party software to copy all the stuff from one team project to the other. But that's not the way it should be. I think I'll just hack into the SQL database of TFS...
William van Strien commented
We aim to utilize TFS as future proof system administration for a new application suite. One of the first things you typically then need/do, is create a TFS project so that you can fill the product backlog. Only in a later stadium the final application identity / name was decided on by business. Due the lack of ability to rename TFS projects our administration now deviates from that name, even while we just started....