Redmine

AFAIK, there shouldn't be any side effect to have 2 projects with the same name.

This restriction was set at the very beginning to be able to identify a project by its name. I finally added the project identifier for that. I'll have a deeper look at this before I remove this restriction.

Is this planned for any coming release, or will the current behaviour be kept for now?

just a positive nudge for this one, it'd be great to have the restriction lifted especially for subprojects within separate parents, I think a warning if that's not the case that there is already a project with that name would be good but for subprojects it should just do a name check against other subprojects in that set.

+1

You can test this yourself (with the usual disclaimers) by editing /app/models/project.rb

Find the line that say "validates_uniqueness_of :name, :identifier"

Remove ":name, " from that line

Save and test (i assume you run this on a copy of your environment). No warnings will be given if you use a previously used name.

/T

Thanks, that seems to work great, now I just need to change the subprojects page heading to include the parent more clearly, I'm thinking make the title "PARENT PROJECT NAME > SUBPROJECT NAME" or something similar.

ok understand that I picked up ruby.... err yesterday, and have little idea currently how things are done but this modification in base.rhtml achieves what I put in the above comment. I think the projects class should include a longname function which returns "[ParentName >>] [ParentName >>].... ProjectName" this would return just the project name if it was a top level or the full path otherwise (that is when more than one level of subproject is enabled) and I think would be handy to use in many situations.

    <h1>
    <% if  @project && !@project.new_record? %>
     <% if @project.ancestors.any? %>
      <%= @project.ancestors.collect {|p| link_to(h(p), :action => 'show', :id => p)}.join(" &#187; ") %> &gt&gt 
     <% end %>
    <% end %>
    <%= h(@project && !@project.new_record? ? @project.name : Setting.app_title) %>
    </h1>

You should have a look at #2788 and r2485.

Jean-Philippe Lang wrote:

You should have a look at #2788 and r2485.

That's brilliant, thanks.

Is this planned for any upcoming release?

what is the status on this? there is no reason for project names to be unique
this is especially annoying when 2 different projects need a subproject named for example 'Modules'

The uniqueness of the project name is at least assumed in the RedmineReceivingEmails functionality.

Holger Just wrote:

The uniqueness of the project name is at least assumed in the RedmineReceivingEmails functionality.

As far as I can tell, the code disagrees on that, see source:trunk/app/models/mail_handler.rb#L161, the project keyword is matched against the identifier only.

I'd be in favor of dropping the uniqueness on project names too, this has become really cumbersome since the projects can be deeply nested.

+1

+1

+1

+1