One project to hold all other projects' components

[GilK]

Hi,

We have a project per releated products (panels project, devices project, server project, mobile project).

Each project includes a bunch of component related to the project.

few projects may share some of their component with other projects.

There is one project - Integration, that is for the integration group which accepts deliveries from all other groups (panels, server, devices, etc.) and tests them.

Does this implemenation make sense?

If so,

I want the Integration project to hold all projects' components.

If an integration girl, finds a bug, she must be able to open the bug on any of the company components.

BTW - what would be the best way to report on bugs in the integration group?

How about opening all bugs under Integration projects and later on (how?) cloning the bugs to the relevant project?

How about other ideas?

Thanks a lot,

Janiv.

[Bob Swift]

Answer to this question:

How about opening all bugs under Integration projects and later on (how?) cloning the bugs to the relevant project

JIRA Clone-Plus plugin would allow you to clone to the relevent project. We use similar technique for issues coming from support system. In our case the component in the original issue determines the mapping to target project via customized clone action. Or just let your user doing the clone determine the target project

[GilK]

So the support team project actually includes all company's components?

Thanks,

J.

[Bob Swift]

In our case the support project has a component that maps to a JIRA development project (for each development project). Each dev project has their own components and those are not surfaced to the support system.