Hi, On 8/8/07, Padraic Hannon <[EMAIL PROTECTED]> wrote: > Managing releases that span multiple projects does tend to be a pain in > Jira as the version field is specific to a project. This means you > cannot query for all tasks for a release across multiple projects unless > you create a separate release field (at least that has been our > experience here at Edmunds).
The idea of splitting the Jackrabbit into multiple Jira projects would be tied to starting independent release cycles for each subproject that is big enough to warrant it's own Jira project. This way we would keep a simple mapping between releases and Jira projects. BR, Jukka Zitting
