We need advice to setup an efficient way to manage the relationships between our libraries and projects. Let me give you an example. Say we have two libraries, Lib A and Lib B, each with its own JIRA project. Each lib has several Versions, each with different enhancement and bugs associated with it. Let's called these different versions A1 and A2 for Lib A and B1 and B2 for lib B.
Now we have project Gizmo which will use these two libraries. Gizmo has its own roadmap, with Version G1 and Version G2 planned. Version 1 will use A1 and B1 while version 2 will use the latest-and-greatest A2 and B2.
We'd like to be able to do a few things:
Now from my limited experience with Jira, I see a few ways to do this:
Any suggestions to handle our use cases?
What a fun problem to work on!
My solution assumes that you are using JIRA Agile (Greenhopper), and instructs on how to create an Agile board to manage all of this.
project in (Gizmo, Lib A, Lib B) AND version in (A1,B1,G1,A2,B2,G2)
ORDER BY Rank ASC
project = Gizmo / project = Lib A / project = Lib B
project = Gizmo AND issuetype = Bug
Let me know how it works out for you! Good luck!
Thanks for your answer, we are actually using Agile so your assumption is correct. I see how your solution could work, but it's based on selective filters. I'd prefer a "deeper" relationship within JIRA itself if at all possible. Otherwise the relationship between project Gizmo and Lib A and B is not immediately obvious to an outsider. The relationship is also not visible outside that particular Agile board.
So far I'm leaning towards creating clone of issues between projects, perhaps using a plugin to facilitate this. The drawback is that creating the proper clones would be manual and someone creating a bug in Lib A for example could forget to clone the bug to project Gizmo.
I might have simplified our use case too much. In fact, our end product is a measurement instrument which includes software and hardware. The SW is composed of instrument-specific SW as well as libraries, which each have their own JIRA project. Same for the HW, it's partly composed on a common HW platform which has its own JIRA project with associated issues and instrument-specific HW (actually there's only one project for instrument specific stuff, mixing both HW and SW together). I'm trying to see how to reproduce in JIRA the links that exist in the real world between all these components.
I'm basically trying to break the silos that tend to exist between projects. John might work on instrument A while bob works on instrument B, but both instrument share half the SW and half the HW. They therefore probably also share half the bugs. John needs to know when Bob finds a bug in a common component that might affect his instrument.
I'm actually quite puzzled that JIRA is not better at handling this kind of cross-project links. Maybe I'm trying to use JIRA the wrong way?
Hi Patrick, Have you found a solution to this yet? I found your inquiry looking for a solution to a very similar problem. In our case we have 'products' that are used for many different 'client projects'. We develop the products for distribution as well, and so have need to track product specific issues in the Product Project directly, but each different Client Project will also introduce issues that we will develop solutions for and add to the product. "Linked Issues" are okay for occasional usage, however, sometimes we may have 100+ issues we have to create for a Client Project, and each Client Project could actually involve several Products, so creating a clone and linking the issues in the Product Project seems overkill. Not to mention our developers would probably want to kill us if they had to manually create hundreds of duplicate issues and link them to the product's issues over and over again. Looking for some solution to this to no avail so far.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs