We have a similar problem to the one posed in the question here: https://answers.atlassian.com/questions/9379983, which does not have any specific answer to help address the problem.
Here's our specific scenario:
We have products that we develop for distribution, as well as client projects that utilize one or more of these products. We use projects to track product creation as well as client project. I'll define these as Product Project, and Client Project, respectively.
We'd like to be able to track issues and progress on those issues in the Product Project, whether the development is initiated from internal planning or from a Client Project. However, we also need to know if the development is initiated in the Client Project, and be able to see progress in the Client Project for all issues in the Product Project that are related.
The easy part is building queries for for Agile boards to show us issues we want to see. We have no problem with that. What we are struggling with is 'where' to actually create the issues, and the idea of 'linked issues' being used does not sit well with our development teams, as it could mean potentially creating hundreds of duplicate issues across multiple projects and manually linking them, which is a complete headache.
We are using Atlassian Cloud, so we are unable to make use of any plugins other than the limited list for Cloud.
Thanks for any input.
Also have a similar situation, essentially there is an entire Program managed under one JIRA Project and they have a field called "Project" which breaks down individual projects. The rationale is that many of these projects are so small, they don't warrant an entire JIRA Project for tracking only a couple dozen issues. Also, the instance of JIRA used was quite old and they have now upgraded to the most recent version and we are implementing and using the JIRA Agile features.
There is workaround which is offered as a Solution in the How to manage issues that affect several projects thread, however I also would like a more integrated solution as part of the JIRA engine. Perhaps something as simple as a foreign key relationship between projects, then we can implement a common field to link issues by "sub"-project; e.g.: "Affects Project" picklist that points to the foreign key. This would still allow us to separate the projects by Agile Board or include them as we see fit.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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