Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Are 300 Jira-projects...too many?

Stefan September 10, 2024

Hello everyone,

Our company produces B2B software. The standardization rate is about 97%, which means that each of our 100+ customers gets a separate software project to customize the remaining 3%. In addition, most customers receive additional projects, each for further special developments.
Our instance therefore has several hundred projects.
Very often time bookings have to be transferred from one project (customer A, project A) to another project (customer A, project B) via tempo timesheets.

We also have two internal projects to further develop the overall product or fix problems and a large Jira service management project where all customer inquiries come together. If the support team there cannot answer a question, a clone is created in a customer project and escalated to a developer.

But we need a better project setup for our 50 users in Software+JSM+Confluence in Standard Cloud .

Maybe one JSM project + one software project for each customer?
Or still one JSM that uses the Organizations field to send change requests to the right customer project? We also thought about JSM licenses for all users and then a JSM project for each customer so that the programmers can chat with the customer without a clone ticket.

In any case, we are looking for a real idea before we start the conversion...do you have a good idea, or someone i could ask specifically?

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events