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
Next: Root
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.
We're looking at how to combine our multiple Jira instances and move from Server to Cloud. We currently have a cloud Jira Service Management instance, which people from our customers access as Customer users (i.e. using the portal only). We have a server Jira Core instance, which customers access as full users. Some of the customers are the same as those people who use Jira Service Management.
I'm trying to decide between migrating the Jira Core users to Jira Work Management under the same URL as Jira Service Management, or setting up a new URL and keeping the two separate.
If I combined them, and I had a user with portal access to Jira Service Management AND full user access to Jira Work Management, but on different Jira projects, what would my experience be like? Will it get too complicated, with people getting stuck in parts of Jira they don't want to be in?
I had also worked on a similar setup before and it is manageable, all you need to do is to make sure to manage the application accesses through Atlassian organization groups and JSM project administrators are well trained towards managing their agents access.
If I combined them, and I had a user with portal access to Jira Service Management AND full user access to Jira Work Management, but on different Jira projects, what would my experience be like? Will it get too complicated, with people getting stuck in parts of Jira they don't want to be in?
The JWM and JSM works quite well along side and should not meddle with each other's functionality if the access are well sorted.
Kind Regards
Utkarsh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, it should be pretty straight forward. As long as you do not add your customers as users in the JSM project they will not be able to see that project when they access a JWM project. We have a similar set up where our internal customers are using JSW for development, but they can only access our JSM projects via Helpdesk Center.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, it shouldn't be hard to figure out. As long as you don't add your customers as users to the JSM project, they won't be able to see that project when they access a JWM project. Our internal customers also use JSW for development, but they can only get to our JSM projects through the Helpdesk Center.
https://community.atlassian.com/t5/Jira-Service-Management/User-with-Customer-access-on-Jira-Service-Management-but-full/qaq-p/1904225/backrooms game
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.