Info |
---|
Due to maintenance, it’s temporarily not possible for customers whose accounts were created after 20 August 2023to add Jira Software projects to Refined sites. If you have any questions, please contact us. |
...
Table of Contents | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Refined for Jira Service Management (JSM) Cloud combines key features from Server/DC with the convenience of the cloud. However, there are also some notable differences between the two products.
...
Due to the parallel setup on Cloud, it becomes possible to combine Confluence and Jira on one and the same Refined site – more on that later.
...
Feature comparison
Feature | Server/ DC | Cloud | Comment about the Cloud feature |
---|---|---|---|
Sites | You can add any project to as many Refined sites as you like. | ||
Categories |
| You group projects with Refined Pages and menu folders instead. | |
Site and Category homes |
| You edit home pages (called landing pages) with the intuitive what-you-see-is-what-you-get Page Builder. Available modules differ slightly from Server/DC, read more in the migration guide below. | |
Navigation menu | Users navigate your site with the navigation menu. | ||
Themes |
| ||
Announcement Banners |
| ||
Promoted Search Results |
| ||
Default JSM Knowledge Base integration | Read more about knowledge bases in step 3 of the preparation guide below. | ||
Custom Knowledge Base integration |
| Read more about knowledge bases in step 3 of the preparation guide below. | |
Third party App compatibility |
| Because Refined Cloud works as a site builder parallel to native Jira, native Jira is not changed by Refined. Therefore, Refined doesn’t impact third party apps that provide functionalities in native Jira, but might impact apps that provide functionalities in the customer-facing portal. | |
Custom domains on sites | - | Give each site a custom URL for quick access and easy recall. | |
Confluence content on sites | - | Getting both Refined for |
JSM Cloud and Refined for Confluence Cloud lets you combine the power of Confluence and Jira on your sites. Read more in step 1 of the preparation guide below. |
Preparation guide
Step 1. 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 2. 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 3. Choose how to implement your knowledge base (optional)
Info |
---|
Refined 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 4. 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 cannot 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 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 5. See how the parallel Cloud setup may impact third party apps
Because Refined Cloud works as a site builder parallel to native Jira, native Jira is not changed by Refined. Therefore, Refined doesn’t impact third party apps that provide functionalities in native Jira, but might impact apps that provide functionalities in the customer-facing portal.
Step 6. Set up a rollout plan
Because Refined 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.
Migration guide
Due to the major infrastructure differences between Server/DC and Cloud, you need to re-create your sites when you migrate. We are working on developing a simpler migration path and will update the migration guide accordingly.
Step 1. Install Refined apps on Cloud
Install these apps on your Atlassian Cloud instance:
Refined for Confluence Cloud (if you want to integrate Confluence content into your sites)
Step 2. Migrate Jira
Upgrade your Refined apps on Server/DC to the latest available version. Then, use Atlassian’s Jira Cloud Migration Assistant to migrate your Jira Server/DC instance to the Cloud.
Step 3. Create Refined sites and add content
Due to the major infrastructure differences between Server/DC and Cloud, you need to re-create your sites when you migrate.
Check out our Get Started guide to learn how to create sites and to move between Jira and Refined. Then, use the Site Builder to add content and arrange it into a structure that is reflected in the site’s navigation menu. To get help from colleagues, delegate administrator permissions. You can give out permissions for your entire Refined instance or for individuals sites.
Step 4. Manage site settings
Manage the site settings for each of your Refined sites, for example:
Set up a custom domain for each site.
Control which kinds of users can access the sites with Site Access Permissions.
Create a cookie dialog.
Step 5. Create and apply themes
Because it’s not possible to migrate themes, you have to re-create and apply them on Cloud. Note that Refined for Jira JSM Cloud doesn’t support third party themes.
Step 6. Create landing pages
Refined for Jira JSM Cloud lets you customize your site’s landing pages with the what-you-see-is-what-you-get Page Builder. Compared to the Layout Editor from Server/DC, the modules in the Page Builder differ a bit terms of functionalities, looks, and availability. Click the links in this table to see compare the documentation.
Layout Editor modules | Page Builder modules |
---|---|
Although the Knowledge Base module doesn’t exist on Cloud, you can use other modules to direct users to your knowledge base. For example, you can add knowledge base links to an Icon module or Image module. | |
Add an Image module with the Navigation Content style. | |
Add an Image module with the Navigation Highlight style. | |
Although the Popular Service Desks module doesn’t exist on Cloud, you can use other modules to direct users to popular service desks. You’ll have to check which service desks are popular, get their URLs, and add these to for example a Links module, Image modules, or Icon modules. | |
- | |
- | |
- | |
- | |
- | |
- | Page Tree (if you have Refined for Confluence Cloud) |
- | News (if you have Refined for Confluence Cloud) |
- | Pages (if you have Refined for Confluence Cloud) |
- | Activity Stream (if you have Refined for Confluence Cloud) |
Need more help?
Have a look at the migration FAQ and the demos & other resources page.
...