...
| Table of Contents | ||
|---|---|---|
|
Step 1. Learn the differences between Server/Data Center and Cloud
Refined Sites for JSM Cloud combines key features from Refined for Server/Data Center (DC) with the convenience of the cloud. However, there are also some notable differences between the two products. Read this page to know what to expect when migrating
Step 2. Consider overhauling your setup
Migrating to a new platform can be a great opportunity to rethink your JSM and Refined setup. We recommend to evaluate what was working well on the Server/DC instance - and what you can improve. You can opt to replicate your Server/DC setup on Cloud with improvements here and there, or see Cloud as a blank canvas to create a totally new setup.
...
Step
...
3. Prepare your base JSM (and Confluence) content
Once you have an idea of your sites' general structure, prepare your JSM projects – and your Confluence spaces too, if you plan to integrate it into your sites. Generally, we recommend to ask yourself the following questions:
Should I restructure my projects/spaces? In other words: which content can be merged and what can be split into separate projects/spaces?
Which projects/spaces should I introduce?
Which projects/spaces can I refresh?
Which projects/spaces can I slim down?
Step
...
4. Choose how to implement your knowledge base (optional)
| Info |
|---|
Refined Sites always respects Atlassian permissions, meaning that content is only shown to users who have access to the relevant Confluence spaces and JSM projects. |
...
The ability to embed request types directly on Confluence pages.
Page tree menus in the left-hand menu of the Confluence spaces.
Confluence modules on your landing pages:
Use the Page Tree module to guide users to self-help articles.
Use the News module to highlight blogs from Confluence spaces.
Use the Pages module to show the most recently updated pages in the Confluence spaces.
Use the Activity Stream module to show recently updated pages in the Confluence spaces.
Step
...
5. See if any limitations apply
You may face some technical JSM limitations on Cloud, depending on your setup. Please read our documentation to get an understanding of the limitations, whether they will impact your migration, and how to prepare.
Limitation regarding | Description |
|---|---|
JSM customers sharing their JSM request | Two limitations depending on customer settings. |
Sharing requests with organizations | When a JSM customer creates a request, they can't add organizations to it. The request view doesn't show which organization(s) the request is shared with. |
Link in customer notification email | When adding a customer to a JSM project, the customer receives an email with a link to complete the signup. After signing up, they are directed to the default JSM project URL, which is (YourCompany).atlassian.net. Due to Refined Sites working parallel to Jira on Cloud, 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.
|
JSM request fields | Although we support most JSM request fields, some have limitations. |
Step
...
6. See how the parallel Cloud setup may impact third party apps
Because Refined Sites for Cloud works as a site builder parallel to native JSM, the app doesn’t change native JSM. Therefore, Refined Sites doesn’t impact third party apps that provide functionalities in native JSM, but might impact apps that provide functionalities in the customer-facing portal.
Step
...
7. Set up a rollout plan
Because Refined Sites works parallel to Jira Cloud, your sites don’t have to be ready directly after migrating. Users can access the native help center while you build your Refined sites. This gives you ample time to get feedback and fine-tune the sites before introducing them to your user base.
...