Are there any negative effects from renaming an RTC project?
I have been asked to rename our RTC project which we having been using for the past 3 year with many custom work items, queries and dashboards plus links to RQM projects. If I go into the project and select "Manage this project area" and then go to the name at the top and change that name, are there any negative impacts to the project, work items, queries, links or dashboards? We have links between that project and two RQM projects so will any of those links break if the project is renamed?
Accepted answer
From the for what it's worth department, my team has a wiki to which we add odd but somewhat frequent occurrences ( e.g. dashboard loosing scroll bar ) and we wrote a post about changing a project/team area name:
Changing Project or Team Area Names
Normally names of objects in RTC/QM are mutable (i.e. user with authority can change). However, there can be temporary unwanted side effects.
- User's bookmarks that have the old project name will be broken and will give "access errors"
- Reporting may show empty lists for report parameters
- Charts will be blank until the historical data jobs run at their scheduled execution time
The run of certain data warehouse jobs will correct the 2nd item, but the first may be more insidious as one has no control over what URI get added to any user's collection of bookmarks.
=======================================
One other answer
This kind of change will mostly affect user-created browser bookmarks. Not much one can do about that really. The association links use the UUID of the linked project (e.g. the last part of the link url might look something like /_u9UlETpXEeKRU9ODuVDBoQ )
It is possible that custom clients might be using the project area name to lookup the project for connection. For example, I maintain a client that is an intermediary between a custom database and an RTC project. The configuration of the client uses the project name, not the UUID.
Basically, changing the name is relatively safe and most interactions won't be disturbed.
It is possible that custom clients might be using the project area name to lookup the project for connection. For example, I maintain a client that is an intermediary between a custom database and an RTC project. The configuration of the client uses the project name, not the UUID.
Basically, changing the name is relatively safe and most interactions won't be disturbed.
Comments
