How can I configure a Jira Cloud project that contains multiple software implementation projects?

[Onboarding _ Support]

 Considering the following:

• I have multiple clients, each with software implementation projects managed using the Scrum methodology with two-week sprints to develop different implementation activities.

• I need reporting at both the client-implementation level to know the percentage of progress, as well as an overall view of all the clients’ implementation projects.

• Is there a limit to the number of issues that can be loaded into Jira or that the screens can support? Because with all the clients and implementations, more than five thousand implementation tasks would need to be loaded.

How can I manage these multiple clients?

1. With a project for each client-implementation?
2. With a single project that considers all clients and implementations as epics?

If I choose option 1, how do I see the overall progress of all client-implementation projects? If I choose option 2, how do I see the individual progress of each client-implementation? Will I have problems with the limit of issues that can be loaded and displayed?

I haven't access to a premium projects type.

Thank you :)

[John Funk · Accepted solution]

Hi @Onboarding _ Support  - Welcome to the Atlassian Community!

I would suggest creating a project per customer. Then use Epics under each project for actual projects for the customer. This way you can see the progress %.

[Onboarding _ Support]

Thank you for your response.
- How could I generate a report that shows the progress of all projects in one place?
- How can I create 50 Scrum projects with the same configurations? Is it possible to clone projects?
-How do I configure bulk task uploads, cause currently not all the fields I have configured in the issues appear?

[John Funk]

1. What do you want the report to look like? How are you determining "progress"?

2. If it is just the configuration, that is easy, just create the project based on an existing project. This is your "template" project more or less. 

3. You can do that with a CSV file. You can export the current issues to just include a couple of fields like the Key and Summary. Then once downloaded as a CSV, add the additional columns for the new fields and upload the CSV in the Settings > System > External System Import

[Onboarding _ Support]

Thank you for your response.

1. I want something in one report like:
Client A - 60% (or 6/10 tasks completed from his implementation)
Client B -  83% (or 19/23 task completed from his implementation)
etc...

2. Ok

3. Ok

[John Funk]

Yeah, that's the hard part because Jira doesn't really make a % complete field available. And definitely not at a project level. 

[Cristian0791 · Accepted solution]

Hi there,

Option 1: Separate Projects for Each Client-Implementation

Pro facts: a)Clear separation of each client’s projects, making it easier to manage specific requirements and tasks.

b)Easier to track progress and report for each client individually.

Cons fact: a)Navigating multiple projects can become hard

b)Reporting across all projects requires manual aggregation or using external tools.

Option 2: Single Project with Epics for Each Client-Implementation

Pro facts: a)Easier management in terms of permissions and access.

b)Simplified reporting since all tasks are in one project. You can create filters and dashboards to track progress across clients.

Cons fact: a)performance may be affected if you exceed Jira’s limits (typically around 500,000 issues per project

b)client progress might be less visible unless properly organized with labels or custom fields( eg. Client 1, Client 2, etc)

You can also try a hybrid approach: using epics for client-implementations within separate projects, if it fits your reporting needs better.

Clients: You have three clients—Client A, Client B, and Client C—each with unique software implementation projects, each consisting of various tasks and activities.

Client A Project:

• Epics: Data Migration, User Training, System Integration
• Tasks: Specific implementation tasks related to each epic.

Client B Project:

• Epics: Requirements Gathering, Development, User Acceptance Testing
• Tasks: Tailored tasks for Client B’s implementation activities.

Client C Project:

• Epics: Design, Implementation, Support
• Tasks: Activities specific to Client C.

Reporting Needs
Client-Specific Reporting:-If you want to report on Client A’s progress, you can easily pull data from their project. You can see how many tasks are completed under each epic, allowing for precise updates to the client.

Overall Progress Reporting:To get an overall view, you can create a dashboard that aggregates information from all three projects.Using JQL, you can pull epic progress from each project. 

Hope this helps.