Multitenant segregation(different customers) in Cloud after migration

Question

We are using Jira software Data Center extensivily and many customers has a full JSW licernse.

As JSW is not built 100% as a tennant system, we do a few hacks the segregate customers like field hide and masking/rewriting a url or two.

Now we want to go to Cloud, and the main concern is actually if the setup (using as multi tenant) is achiveable in the Jira Cloud - or we should (need to) force all to JSM...

We have customer that dont want their names or anything shared with other customers.

Forcing all to JSM will have a huge (negative) impact on the collaboration with the close customers...

Anyone who has tried or are thinking about the same problem... I really dont want to foce the PM department or others into a new cloud service to use instead of Jira.

I have been thinking the though of multiple sites (Requires enterprise - expensive)... but that will spawn many, many sites over time....

Rebekka Heilmann (viadee) · Answer

Ah sorry - yep, missed that detail indeed ;)

No there are no built-in mechanisms to hide users from each other within one site. You could limit the global "browse user" permission, but then they can't find any user, not even ones from their own company.

Normann P_ Nielsen _Netic_ · Answer

You missed the point - this is for customers with "full JSW license."

Hence a "Jira" license in Cloud

Hence there is no "Organisations" - as I belive its only available in JSM (in cloud also)?

Rebekka Heilmann (viadee) · Answer

Hi @Normann P_ Nielsen _Netic_

i don't quite get what your concern is exactly?

If you sort your customers into Organisations, you can restrict the Request sharing to each Org and nobody sees each other's Email adresses.
There's not really a big difference to Data Center when it comes to that.

With Premium you can create different help centers to have seperate UIs between JSM projects.