You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have an internal discussion with my team mates to find out which is the best and optimal way to organize our teams.
We are a Change Management team and will propose a new way of using Jira to the rest of the employees.
First option is to have one Service Desk which will be used by the entire company. Minuses here are:
|All departments + bands have access to change|
Second option is to have one Service Desks on each project(team). Minuses here are:
|all departments have access to the band project|
As a note, one change ticket will be used by multiple departments(CMS, R&D, ICT + others ). Who has access in the CMS project should not be able to change the project settings just pick up requests and edit a certain queue.
Is there anyone who has any suggestion on this organisational idea, pros vs cons on each option ? which one is the best ? I tend to chose first option as it looks more convenient and organised.
Thank you in advance,