From: Jon H. <jd_...@ya...> - 2009-02-12 16:55:50
|
Can anyone shed any light on why sub-projects have to be unique over the whole of mantis? 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. Cheers. ----------------------- N: Jon Hardcastle E: Jon@eHardcastle.com '..Be fearful when others are greedy, and be greedy when others are fearful.' ----------------------- |
From: Gianluca S. <gi...@gm...> - 2009-02-12 17:06:42
|
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. -- Gianluca Sforna http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna |
From: John R. <jr...@le...> - 2009-02-12 18:03:07
|
On 02/12/2009 11:55 AM, Jon Hardcastle wrote: > Can anyone shed any light on why sub-projects have to be unique over the > whole of mantis? 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. Perhaps it would be useful to know that you can link a project as sub-project to multiple main projects. Eg: Create three projects: A, B, and C Set C as a sub-project of A Set C as a sub-project of B Resulting hierarchy: A B \ / C Cheers -- John Reese LeetCode.net |
From: Glenn H. <thr...@lo...> - 2009-02-12 21:06:35
|
On 12-Feb-09, at 1:03 PM, John Reese wrote: > On 02/12/2009 11:55 AM, Jon Hardcastle wrote: >> Can anyone shed any light on why sub-projects have to be unique >> over the >> whole of mantis? 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. > > Perhaps it would be useful to know that you can link a project as > sub-project to multiple main projects. > > Eg: > Create three projects: A, B, and C > Set C as a sub-project of A > Set C as a sub-project of B > > Resulting hierarchy: > > A B > \ / > C This was the original intent when the feature was added. This would allow common code to show up in the bug lists for multiple projects. It was also done to allow private projects (with different teams) to be aggregated by managers. From your description, you probably want to use categories, not subprojects. -- Glenn Henshaw Logical Outcome Ltd. e: thr...@lo... w: www.logicaloutcome.ca Mantis Developer and User since 2002 |
From: Jon H. <jd_...@ya...> - 2009-02-14 10:54:46
|
--- On Thu, 12/2/09, Glenn Henshaw <thr...@lo...> wrote: > From: Glenn Henshaw <thr...@lo...> > Subject: Re: [mantisbt-help] Unique project names > To: "Help with Mantis" <man...@li...> > Cc: Jon@eHardcastle.com > Date: Thursday, 12 February, 2009, 9:06 PM > On 12-Feb-09, at 1:03 PM, John Reese wrote: > > > On 02/12/2009 11:55 AM, Jon Hardcastle wrote: > >> Can anyone shed any light on why sub-projects have > to be unique over the > >> whole of mantis? 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. > > > > Perhaps it would be useful to know that you can link a > project as > > sub-project to multiple main projects. > > > > Eg: > > Create three projects: A, B, and C > > Set C as a sub-project of A > > Set C as a sub-project of B > > > > Resulting hierarchy: > > > > A B > > \ / > > C > > This was the original intent when the feature was added. > This would allow common code to show up in the bug lists for > multiple projects. It was also done to allow private > projects (with different teams) to be aggregated by > managers. > > From your description, you probably want to use > categories, not subprojects. > > I suspect we are using the systems in the wrong way or our process is strange but we are going from a home grown system to mantis, and I am trying to arrange abit of 'meeting in the middle' betwen what 'we' do, and what 'others' seem to do. We basically have a product that is made up of several subprojects each with their own product mangers etc etc. We need categories at this level because each sub-product has areas as you might expect so we have Products ->Our Product ->Area 1 ->Area 2 ->Another product -> Area 1 -> Area 2 This is all fine and can mostly do what we want within this frame work. But what we also have is a 'system test' area that ideally will mimic the above layout - hence the collision on project names. We want to be able to do it though so we can maintain the product leaders and just 'move' a fault into the system test area that has different version numbers etc. Mangers will be kept aware of what is going on because their 'own' the projects in both cases. We can frig the naming calling it 'SysTest-Our product' but if we have multiple system test cycles going it they want to separate the issues out. Does this make it clearer what we are trying to do? I know we can use versions in this arena to some extent but like i say it is meeting the middle I am trying to achieve. ----------------------- N: Jon Hardcastle E: Jon@eHardcastle.com '..Be fearful when others are greedy, and be greedy when others are fearful.' ----------------------- |
From: Jay B. <jay...@gm...> - 2009-02-16 22:28:01
|
Could tags help you with this? We're finding tags to be very flexible and useful for loose associations like this. They are usable from the filter-list of issues. Could tags be abused? Sure, but they could help subdivide categories of issues within product lines. + jay Jon Hardcastle wrote: > > --- On Thu, 12/2/09, Glenn Henshaw <thr...@lo...> wrote: > >> From: Glenn Henshaw <thr...@lo...> >> Subject: Re: [mantisbt-help] Unique project names >> To: "Help with Mantis" <man...@li...> >> Cc: Jon@eHardcastle.com >> Date: Thursday, 12 February, 2009, 9:06 PM >> On 12-Feb-09, at 1:03 PM, John Reese wrote: >> >>> On 02/12/2009 11:55 AM, Jon Hardcastle wrote: >>>> Can anyone shed any light on why sub-projects have >> to be unique over the >>>> whole of mantis? 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. >>> Perhaps it would be useful to know that you can link a >> project as >>> sub-project to multiple main projects. >>> >>> Eg: >>> Create three projects: A, B, and C >>> Set C as a sub-project of A >>> Set C as a sub-project of B >>> >>> Resulting hierarchy: >>> >>> A B >>> \ / >>> C >> This was the original intent when the feature was added. >> This would allow common code to show up in the bug lists for >> multiple projects. It was also done to allow private >> projects (with different teams) to be aggregated by >> managers. >> >> From your description, you probably want to use >> categories, not subprojects. >> >> > > I suspect we are using the systems in the wrong way or our process is strange but we are going from a home grown system to mantis, and I am trying to arrange abit of 'meeting in the middle' betwen what 'we' do, and what 'others' seem to do. > > We basically have a product that is made up of several subprojects each with their own product mangers etc etc. We need categories at this level because each sub-product has areas as you might expect so we have > > Products > ->Our Product > ->Area 1 > ->Area 2 > ->Another product > -> Area 1 > -> Area 2 > > This is all fine and can mostly do what we want within this frame work. But what we also have is a 'system test' area that ideally will mimic the above layout - hence the collision on project names. We want to be able to do it though so we can maintain the product leaders and just 'move' a fault into the system test area that has different version numbers etc. Mangers will be kept aware of what is going on because their 'own' the projects in both cases. We can frig the naming calling it 'SysTest-Our product' but if we have multiple system test cycles going it they want to separate the issues out. > > Does this make it clearer what we are trying to do? I know we can use versions in this arena to some extent but like i say it is meeting the middle I am trying to achieve. > > > ----------------------- > N: Jon Hardcastle > E: Jon@eHardcastle.com > '..Be fearful when others are greedy, and be greedy when others are fearful.' > ----------------------- > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > mantisbt-help mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-help |
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. |
From: Shawn H. <nya...@gm...> - 2009-02-12 20:39:27
|
Hi, I wonder if I can offer an alternative arrangement here? We used to run multiple projects like this and it was an admin overhead at times. We then changed the severity enum string to have a 'feature' type. This allowed all the bugs to remain in the one project and can be filtered on easily enough. This is how we run it now across multiple products and it works well. Product Managers can see only the features if they wish and maintenance developers can see only the bugs if they wish. I know this is not the answer you're looking for, but I thought I would offer what we do. You may be able to adjust Mantis to allow non-unique Project names via a code change, but you will need to follow this change through on every upgrade you do. (like I have to with all my customizations) Good Luck Shawn On Fri, Feb 13, 2009 at 9:15 AM, Jennifer Mullen <jm...@ps...> wrote: > 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. > > > ------------------------------------------------------------------------------ > _______________________________________________ > mantisbt-help mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-help > -- nya...@gm... |