...
Expand |
---|
title | Do my Refined for Jira sites work the same on Cloud as they do on Refined for Server/DC? |
---|
|
Refined for Jira Cloud combines key features from Server/DC with the convenience of the cloud, but there are also some notable differences between the two products. On Server/DC, Refined is added on top of Jira: when enabled globally, Refined acts as a skin applied to the JSM help center. On Cloud, Refined is a site builder that runs parallel to Jira. This means that: The Refined sites dynamically pull and expose JSM portals onto a parallel Refined site, so all the changes you make in Jira are instantly reflected on your Refined sites. Users create and view JSM requests on your site. Admins still create and set up the project and request types in native Jira, and if they make a change to a project it is instantly reflected on the Refined site. We don't have control over the (YourCompany).atlassian.net URL. This means that we can't redirect users from a (YourCompany).atlassian.net site to a Refined site.
It’s easy to combine Jira and Confluence into one Refined site if you get both the app Refined for Jira Cloud and the app Refined for Confluence Cloud. This opens up many new ways of using Confluence and Jira – some examples: It enables you to build an intranet that features Confluence spaces and JSM service desks, for example to contact HR and IT. Similarly, you can create an outside-facing help site that features not only a service desk but also a full-blown knowledge base.
See a full feature comparison between Refined for Jira on Server/DC and on Cloud. |
...
Read the in-depth preparation and migration guides:
...