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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

one vs multiple projects

We are a service provider offering IT services for many customers (B2B). For the customers we offer both individual solutions and product-based solutions that we develop ourselves.

Each product is organized in a "JIRA software" project. These Scrum teams have no customer contact.

For the services we provide to our customers, we implement "JIRA service management" on premise - for incidents, service requests and changes.

Unfortunately, we do not have the ability to have every issue implemented 100% by a cross-functional team. We are now faced with the challenge

  • of having to decide whether all customer requests should be organized in a single project
  • or whether we should set up different projects.

There are also requests, for example larger customer projects, that need to be distributed across different teams or skill groups.

What solutions does "JIRA Service Management" in conjunction with "Jira software" offer here? Are there any best practices?



Log in or Sign up to comment