You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi Atlassian Community!
I would like to get your feedback about this topic: how to organize Jira projects in a software development based on a product line / platform and in the derived products.
To begin with, I would like to let you know that currently we are using one big Jira project to track all the issues related with our platform or software assets. We are managing in the same Jira project all the software components available in our platform, that can be used to derive products, and even all the "auxiliary" app-s used for testing or diagnostics purposes. Even docs-related issues are in this unique project.
I am fully convinced that this approach has been the more efficient during the first development phases, with all the info centralized in the same projects. I am not so sure now that the project is evolving to a maintenance phase, with independent releases for the "main" platform and for the "auxiliary" app-s, but let's leave this discussion for another day, and let's assume that we have one unique Jira project for the whole platform.
In our product line based approach, we are starting to derive more and more products from the platform. Until now, we were adding this products in the same Jira project but, it's becoming bigger and bigger and the question has arised. Is this the best approach or should we switch to a model where we create a Jira project for each derived product?
Whereas new versions of the platform are released more or less periodically, new versions of the derived products are released on demand and with no temporal relation with the platform. Moreover, we need to version both the platform and each of the derived products, each of them with its own version. But I am afraid that having so many projects will become unmanageable.
Nevertheless, we need to keep the issues at product level linked with the issues at platform level (where the software components are mainly included).
Could you give me some advice about the best practices regarding this?
here are some thoughts that might help you. Please comment if I misunderstood your requirements.
Now with that in mind, let's talk about your concern of keeping Jira manageable with increasing amount of projects.