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.




No concept of issue dependencies?

web-app

Gemini doesn't seem to have a proper mechanism for issue dependencies. Example:

Issue #1: Implement online help framework Issue #2: Add quickstart guide to online help Issue #3: Add installation guide to online help

Obviously Issue #1 has to be closed before #2 and #3 can be closed. But how can I specify this in Gemini?

Yes, I know there's a feature for specifying Sub-Issues. I could specify #1 as a sub-issue of #2 and of #3. That would prevent #2 and #3 from being closed before #1 is closed. But #1 is actually the larger parent issue -- implementing online help -- and #2 and #3 are sub-issues of that major issue. Yet Gemini would have me do the inverse: Make #1 a child of the other two, which really doesn't make sense.

Is there no way to specify that one issue merely "depends upon" another, as in the other issue tracking systems I'm used to? Or is the sub-issue mechanism the only way?
Trevor Harmon
· 1 		Trevor Harmon
Monday, August 23, 2010, 1:23:55 AM
Replies (5)
helpful
0
not helpful

You should use sub issues, #1 will be the parent and #2, #3 the sub issues.
Mark Wing
· 9108 		Mark Wing
Monday, August 23, 2010, 10:29:58 AM
helpful
0
not helpful

Right, I know I can do that, but it produces a hierarchy that looks like this:

--- Add quickstart guide to online help --------- Implement online help framework --- Add installation guide to online help --------- Implement online help framework

which is nonsensical, don't you think? If there has to be a hierarchy, it should look like this:

--- Implement online help framework --------- Add quickstart guide to online help --------- Add installation guide to online help

But this is not possible in Gemini without destroying the necessary dependency relationships. (e.g., "Add quickstart guide" depends on "Implement help framework" being implemented first).

If, instead of a sub-issue relationship, I could simply say "Issue X depends on Issue Y", then the issue dependency graph would automatically have the desired hierarchy.
Trevor Harmon
· 1 		Trevor Harmon
Wednesday, August 25, 2010, 9:58:42 AM
helpful
0
not helpful

Understood, thank you.

We do not enforce the order in which issues must be closed.
Harvey Kandola
· 212 		Harvey Kandola
Wednesday, August 25, 2010, 10:40:41 AM
helpful
0
not helpful

[quote user="HarveyKandola"]We do not enforce the order in which issues must be closed.[/quote]

Have I misunderstood something? Your documentation says otherwise. From Section 2.2.11: "A Parent Issue cannot be closed until all its children have also been closed."
Trevor Harmon
· 1 		Trevor Harmon
Wednesday, August 25, 2010, 11:06:29 AM
helpful
0
not helpful

Yes, we enforce this. But don't enforce the order of sub issue closure.
Mark Wing
· 9108 		Mark Wing
Wednesday, August 25, 2010, 1:49:20 PM