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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,555,911
Community Members
 
Community Events
184
Community Groups

One or multiple projects?

I have just convinced a client to chose JIRA Service Management and now I'm in charge of the implementation project 😨

I have been playing around quite a while in the free version so I'm pretty sure how the product works. I just have a question about multiple projects or not.

The way I have set the test up is by using one project per support apartment. The problem is that the client has one general support mail that most of the tickets arrive to. I want to set up automations that dispatches the tickets according to keywords, but that causes problems when I use multiple projects.

Would you recommend setting up one project for the client and visualizing the tickets based on tags instead?

Thankful for answers as they will guide me in this critical stage.

1 answer

1 accepted

2 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 12, 2021

Hi Olof,

Based on your scenario, I would probably use just one project on the front end to capture the requests. Then you can either add tags (Labels or Components) to get the tickets to the right team. Or you could even spawn off separate not JSM projects (Classic Software projects) to clone the ticket and work in a normal development environment. 

I would use a field that captures certain values in a dropdown to determine how the tags get labeled. Then you can you automation if needed. 

Clark Everson
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 12, 2021

Hi Olof,

I would agree with John here. And then I would provide the feedback based on the requests and the categories etc you can break it off into other service desks later if the one becomes too overwhelming or they want more people/teams to be in the service desk. 

Usually with a service desk, once people see the benefits, more people want it for their team versus email.

 

Clark

Like Olof Nysten likes this

Thank you for your answers. I think that one project at a start and maybe later create more projects sounds like a very good idea. I will go with that.

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events