View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008709 | mantisbt | other | public | 2008-01-06 17:34 | 2008-07-24 16:50 |
| Reporter | bpeikes | Assigned To | vboctor | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Summary | 0008709: Project names should not have to be unique | ||||
| Description | Why do project names have to be unique? I have three projects, i.e. customers, CustomerA, CustomerB, CustomerC, each of them should have a subproject called Website. I haven't looked at the sql tables yet, but I can't imagine that there should be any reason to have unique project names, that is if you have ids for the projects. | ||||
| Tags | No tags attached. | ||||
| duplicate of | 0006227 | new | Project names unique? | |
| has duplicate | 0008848 | closed | ryandesign | wishing sub project in different trees with identical name |
|
Another problem caused by the fact that sub-projects are just implemented (AFAICS) as projects which are then attached to a given project. It could be solved by making sub-projects unique to projects which would solve some usability problems as well. Possible solution were suggested to the mailinglist during a discussion about usability. |
|
|
But please be aware that moving "subproject" between "project"s must be possible indifferent ot the implementation way. @schoenfeld: Do you have a link to that discussion? Thanks! |
|
|
I think he's referring to: http://thread.gmane.org/gmane.comp.bug-tracking.mantis.devel/1950 |
|
|
Thanks for giving the link. It's worth reading. Some of the aspects I'd underwrite; especially when planning to have more than one project manager (at this time I'm alone with administration), who are responsible for its project (and sub projects if want's to use) |
|