ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Allow project identifier to be changed (Feature #1131)

Added by Colan Schwartz at 2012-08-30 12:00 am. Updated at 2012-09-03 11:06 pm.

Status:Open Start date:2012-08-29
Priority:Normal Due date:
Assignee:- % Done:


Category:User interface
Target version:-
Remote issue URL: Affected version:3.3.0


It would be great if users could change the project identifiers (and hence URLs) for projects.

Is this something that's feasable?

There's actually a Redmine discussion about having these be automatically generated. That's a good idea in that IDs wouldn't locked into particular textual descriptions. See for details. I couldn't find an exact match for this issue in the other queue.

Associated revisions

Revision 715c9d16
Added by Eric Davis at 2010-05-23 05:16 am

Refactor AuthSourcesController to support non-LDAP sources. #1131

git-svn-id: svn+ssh:// e93f8b46-1217-0410-a6f0-8f06a7374b81


Updated by Luke Carrier at 2012-09-03 11:06 pm

Semantically, I understand the motivation for not encouraging these identifiers to be modified -- since they're used in URLs throughout the application (not just those you get in emails, but also within the wiki, notes and even SCM commits) and the fact they're not actually displayed within the views, it's difficult to justify modifying them. Despite this, it is already possible - those who have access to the production databases for their installations can change it via an SQL query with no adverse effects (other than breaking links):

1UPDATE `projects` SET `identifier` = 'new-identifier' WHERE `identifier` = 'old-identifier';

Also available in: Atom PDF