How to manage multiple rollout projects in JIRA?

[Jatin Malhotra]

Hello Experts and Friends,

We are planning to schedule multiple RollOut Projects using JIRA where each project is of a duration 5 months considering a total of 5 projects (as Wave 1, Wave 2 upto Wave 5). Also, consider the number of countries to Go-Live differ in each Project Wave (e.g. Wave 1 has 1 country, Wave 2 has 4 countries, Wave 3 has 5 countries etc.). Now for each Wave a combination of scope consists of similar set of requirements  for all countries (irrespective) and there could be some country specific localization requirements, as well. Also, we would like to use standard JIRA reporting for Pie Char - Status, Created Vs. Resolved etc.

Please share your experiences how to manage this situation in JIRA? I would sincerely appreciate your experiences and out of the box solution.

Kind Regards,

Jatin

[Yuri Lapin _Release Management_]

Hi @Jatin Malhotra

Trust you are well.

If you want to take a Release centric view to it - aka Rollout product, release or feature plus you do ongoing - we have a solution for it. We allow to package cross-project deliverable into programs and orchestrate them on Kanban board or Timeline view.

Check out Release Management & Roadmaps App or request a quick demo here:

https://docs.google.com/forms/d/e/1FAIpQLSdvVBm5KK5wTNosLqyP9iKUI8GOoqZn8kQEyV-1yAOJZEwKxQ/viewform 

Cheers,

Yuri. 

[Deepanshu Natani]

Hi @Jatin Malhotra 

You can create 5 different projects, each project can have its own release cycle/ rollout plan.

Within each project, countries can be defined using a custom field/ components (as per your needs).

And you should be easily able to get all the needed reports based on filters.

[Kris G _Alacriz_]

Hi @Deepanshu Natani , 

Don't you think this requirement can be met using a single Jira project, assuming @Jatin Malhotra is talking about a company-managed Jira solution ? 

As  you rightly said, countries can be captured using custom fields or components and reports based on filters. As all projects have similar configurations (issue types, screens, fields, permissions, etc.), is there a compelling reason to create 5 different Jira projects ? And I believe localization requirements can be managed with a single Jira project too unless there is something that is not too obvious to warrant that approach. 

Your inputs are welcome. 

best,
Kris