Re: [Mantisbt-help] Subproject Usage

[Glenn H. <thr...@ma...>]

   I have some fixes that I will add to 1.1 to allow inheriting  
categories and versions from parent projects that I plan to add to 1.1.

    ... Glenn

On 3-Aug-06, at 9:16 PM, Jennifer Mullen wrote:

> I am not grokking how subprojects are supposed to be used, and not  
> finding the answers to my questions in the manual or the forums. If  
> some one could take a minute to help me out, I'd really appreciate it.
>
> I use Mantis to track issues in our course management system. I  
> have two projects named "Bugs" and "Enhancements." As each of these  
> projects relate to the same application, the versions are the same  
> for each. Each project also has three custom fields, which indicate  
> the ticket number, issue number, and status of each item in our  
> vendor's support tracker and issue database (yes, this is rather  
> tortured). The two projects also have the same categories defined.
>
> When I created the parent "CMS" project and made the other two its  
> sub-projects, I had a few goals in mind:
>
> 1. Define application versions in one project, CMS, and have them  
> "trickle down" into the sub-projects.
>
> 2. Define categories in one project, CMS, and have them trickle  
> down into the sub-projects.
>
> 3. In the filters box when viewing the CMS project, click on the  
> "Vendor Issue #" filter and see a list of issue numbers for both  
> sub-projects.

   Can you describe this in more detail?

>
> Unfortunately, none of these actually work as I'd like them to.
>
> Am I missing something, or is this functionality not currently  
> present in Mantis?
>
>
> Thanks,
>
> 	-J.
>
> --
> Jennifer Mullen <js...@ps...>
> Consulting and Support Services
> a unit of Information Technology Services
> Penn State University
>

-- 
Glenn Henshaw                     Logical Outcome Ltd.
e: thr...@ma...              w: www.logicaloutcome.ca
Mantis developer and user