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.

When trying to add sub-project, receive error of "Identifier has already been taken". (Bug #932)

Added by Brian Merritt at 2012-03-15 04:26 pm. Updated at 2012-03-20 09:30 am.

Status:Closed Start date:2012-03-15
Priority:Normal Due date:
Assignee:- % Done:


Target version:-
Remote issue URL: Affected version:


We have a project called Product that we have a variety of sub-projects in. When trying to create a new sub-project with certain names, we get the error "Identifier has already been taken" and are unable to create the sub-project with the chosen name. Other sub-project names work. The names that do not work are not associated with any current Projects. Some (all?) of them were previously associated with a custom field called 'Features', but that custom field has been removed. Any ideas? This is blocking our ability to organize our projects the way we want to. :(

Associated revisions

Revision a340d8c9
Added by Jean-Philippe Lang at 2008-04-13 11:12 am

Better error message and AR errors in log for failed LDAP on-the-fly user creation (closes #932, #1042).

git-svn-id: e93f8b46-1217-0410-a6f0-8f06a7374b81


Updated by Holger Just at 2012-03-15 05:21 pm

Project identifiers have to be globally unique to be able to uniquely identify projects by their name. So you can't have two projects with the same identifier, regardless of their nesting or activation state. Thus you also have to consider locked projects.

  • Priority changed from High to Normal

Updated by Brian Merritt at 2012-03-15 07:58 pm

Understood. We do not have any other Projects using these names, locked or otherwise.

Updated by Felix Schäfer at 2012-03-16 12:11 am

Maybe the error message doesn't reflect the error correctly either, could you post an example of an actually failing identifier?

Updated by Brian Merritt at 2012-03-19 09:25 pm

This is a non-issue. An archived project was using the identifiers that weren't working. Sorry for wasting your time.

  • Status changed from Open to Closed

Updated by Felix Schäfer at 2012-03-20 09:30 am

No problem, thanks for reporting back :-)

Also available in: Atom PDF