Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Suggestion for component re-use across releases

web-app

I'm evaluating Gemini as a possible issue tracker for one of my clients - a software developer that has a number of products, each comprised of several components. Some components are shared across products.

Each product has its own release schedule.

So a component is a first-class entity in its own right, and may belong to one or more release projects. The tight hierarchy of Gemini doesn't support this on face value but I was wondering if any current Gemini users have a similar business operational model and how they use Gemini's concepts of "projects", "components" and "versions" (and their attributes) to support the process?

Any help much appreciated.
cyberfuel
· 1 		cyberfuel
Saturday, February 7, 2009, 7:42:12 AM
Replies (2)
helpful
0
not helpful

cyberfuel,

Maybe shared components are Projects in their own rights given their first-class status?
Harvey Kandola
· 212 		Harvey Kandola
Sunday, February 8, 2009, 2:54:13 PM
helpful
0
not helpful

Hi Harvey,

Yes, I think that is what we would need to do. I was hoping to find a tracker that had a concept of "product" that consisted of "components" where components were shared between products. However, with Gemini we will need to elevate my customer's idea of a component to be a project and then manage product releases through project versions tied to an external register of which project versions map to a product release.

The only difficult part is that non-technical users don't necessarily know what project to log an issue against - they see an issue as being a product issue. This then needs to be interpreted by a developer or technical analyst to ascertain what project is causing the issue. We could model this by setting up projects for each product and then moving or linking issues down at the software project level. Could be confusing.

I like Gemini a lot and it is still a contender.

Andrew Goldie
http://www.cyberfuel.co.nz
cyberfuel
· 1 		cyberfuel
Sunday, February 8, 2009, 8:56:30 PM