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'am in the middle of organizational changes in my company. Creating processes, changing tools etc. We have three core groups: developers (including testers and project managers), support and sales team. We choose to switch to Atlassian products.
At a first we decided to change organization in our support team thus we bought Jira Service Desk and created simplified ITSM processes (Issue Management, Service Request Management, Change Management and Problem Management).
I'am wondering about your experience, opinion and lessons learned about Jira Service Desk organization.
I'am thinking about two solutions:
For now I can see following pros and cons for both:
One project for internal and external customers.
Two projects. First for internal and second for external customers.
Which is better solution and why? Maybe some of you have tried both ways and can share the knowledge. I don't want to invent a wheel once again ;)
In the future we want to have Jira Software and Jira Core for other teams. For support team we are thinking about Statuspage (is there a way to separate internal and external issues?). Maybe integration with other Atlassian product (Bitbucket, Hipchat etc).
@Jack Brickey Thank you very much for your answer. I'm pretty convinced that separate project are the right direction :)
sounds good and good luck. As you move forward and have further questions the Community is a great place to rely on. Many question are already answered.