Nested Components or Custom Hierarchy

[plex]

Suppose you have two products where components of one product are also related to another product. Is it possible to create a "super product" which contains a set of components of product A and B?

I've searched for an issue tracking supporting this feature .. is mantis able to do this?

[leblancma]

Suppose you have two products where components of one product are also related to another product. Is it possible to create a "super product" which contains a set of components of product A and B?

I've searched for an issue tracking supporting this feature .. is mantis able to do this?

Have you thought about the possibility of creating a project to represent the "super product", and then create an issue for each component. You could then clone the issues which are also part of another "super product".

Interesting use of Mantis - a little like people who use a genealogy program to record the pedigree of race horses.

[plex]

Yes I could do this the way you described, but sometimes you don't have visibility. You don't know about the existence of other components that might have impact when creating an issue on a certain product.

My goal is to create virtual products containing products, or components of other products, that have possible impact when raising an issue against it.

When raising an issue on a certain component of a product, you know that another product also uses the same component, and that this issue has also possible impact on it.

Creating a hierarchical view would definitely increase visibility here.

[simone.girlanda]

I think that this is similar to what I'm also asking:

http://www.mantisbt.org/forums/viewtopi ... nts#p18829

I did some customization in this direction, but a lot of work is needed to complete it.

I'm looking for somebody that can share effort and sponsorship.