From: Jennifer M. <jm...@ps...> - 2009-02-12 20:16:05
|
On 2/12/09 12:06 PM, Gianluca Sforna wrote: > On Thu, Feb 12, 2009 at 5:55 PM, Jon Hardcastle<jd_...@ya...> wrote: >> > Can anyone shed any light on why sub-projects have to be unique over the >> > whole of mantis? > > subprojects are really "projects", and you can't have two of them with > the same name. > >> >This is causing us some problems as we have several quite >> > level areas, then within this we have areas of responsibility and again >> > within this categories. >> > >> > It is proving troublesome to have different names for the same things.. in >> > slightly different areas. > > I am not sure I understand you here. maybe an example would be > enlightening to make a more sensible comment. > I have an example. I have several projects in Mantis. For various reasons, some of the project managers prefer to have two subprojects: one for bugs and one for feature requests. In other words, what they want would look like this in the project selector: Project A >> Bugs >> Enhancements Project B >> Bugs >> Enhancements Project C >> Bugs >> Enhancements Instead, what I have to do is this: Project A >> Bugs (Project A) >> Enhancements (Project A) Project B >> Bugs (Project B) >> Enhancements (Project B) Project C >> Bugs (Project C) >> Enhancements (Project C) If projects with identical names were allowed, then I could give my users what they want, which is the first situation. I don't see a good reason to not allow this since the project's name is not its identifier in the database. -J. |