Single team, multiple projects with dependancies and shared code

[Gili Zeevi]

Were trying to figure out the best practice of setting up JIRA for this specific case:

• A single multidisciplinary team.
• Multiple projects (at least 3) with some dependancies as well as some reusable code/components shared between the projects.
• A way to represent features with multiple tasks (Epics or components)
• Use of basic roadmaps to share plans and team progress with the team and external stakeholders.
• Weekly releases (versions) for all projects.

An example:

• Projects: AAA, BBB, CCC
• CCC functionality is shared between AAA, BBB (Assume something like a framework or a large software component)
• AAA & BBB have their own unique requirements

In the past we used a hosted JIRA solution (with an old version) which didn't allow us to use roadmaps. We used a single JIRA project and represented multiple projects (AAA, BBB, CCC) with epics. This will likely not work well with basic roadmaps.

[Gaurav]

Hello @Gili Zeevi 

The basic roadmaps can be used with a single project (epic level tracking) whereas advanced roadmaps provide multiple teams and projects functionality.

With the setup you have, I believe the basic roadmap would be useful. The detailed functionalities can be explored here.

Kindly accept the answer if it helps.