Hi,
Not so much issue links , but maybe version or project links . For instance , we are building a web project , but we know it cannot be deployed without the completion of a back end project supporting the services the web project needs. So we have a number of tasks in project A that must be completed and the project released before project B can be released, so from a project management perspective am trying to decide how best to track and manage progress and release. This also affects testing as well as deployment. At present we have a single "fixed in release:" field for a version, but a version can only exist in 1 project and cannot span 2 projects. Basically what we have is a release that spans 2 Gemini projects (it could in fact span more but for us 2 is what we have). It is perhaps the concept of a product release that has several projects, or maybe in Gemini terms a main project with sub projects.
Hope this make sense - am trying to decide the best way to approach this
Cheers
Steve