Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

PAGE UNDER CONSTRUCTION

In this article we explain the differences between Refined for Jira Cloud and Refined for Jira Server and DC to help you decide which might be best for your clients.

Refined for Jira - What's the same on Cloud and Server?

  • Refined for Jira Cloud, Server and DC for the most part function the same on Cloud and Server. The key features such as the theme editor, layout editor, site builder for site organization, site structure and content modules are the same across hostings. There are some differences we explain below.

Refined for Jira - What are the differences on Cloud and Server?

Refined for Jira Cloud

Refined for Jira Server and DC

Refined for Jira Cloud is an app connected to Jira. It reads the API’s from Jira Cloud and pulls in the data. This means on Cloud you will always have native Jira, together with your Refined version of Jira. Whereas on Server when Refined is installed onto Jira a Jira Service Desk help center and portals will be replaced with the custom look and feel you’ve created in Refined.

On Refined for Jira Server and DC the app is installed onto Jira. Refined on Jira Server replaces the ‘customer facing’ pages. So the service desk portals and help desk is replaced with Refined. Jira projects will remain in native Jira and it is only when a Jira project is added to Refined in the site builder that it creates a Refined version of that project. Think of it as a customer facing portal for a Jira project.

Refined for Jira Cloud is hosted by Refined at refined.site.

Refined for Jira Server DC is hosted in the same place as your Jira instance.

On Refined for Jira Cloud you can pull Atlassian content from Jira, Jira Service Desk and Confluence and expose the content on Refined’s interface.

You can choose to activate only Jira/Jira Service Desk as the source of content to display in Refined. Or you can choose to activate both Jira/JSD and Confluence. Please note, you will need to purchase both Refined for Jira and Refined for Confluence Cloud to display both Jira and Confluence content.

Think of Refined as a CMS or website content builder for Atlassian Tools.

Use the site builder (admin section) to organize the site structure and navigation. Once the content sources are activated, add in Jira projects and Confluence spaces to your site builder navigation.

Site Builder in Cloud:

On Refined for Jira Server DC you can pull and display content from Jira and Jira Service Desk on your Refined sites.

If you’ve connected a Confluence instance, you can display knowledge base articles from as many Confluence spaces as you wish using the layout editor modules (in native Confluence you can only connect one space). Refined will display knowledge base articles in-frame. Learn how to configure knowledge base settings.

Use the site builder (admin section) to organize the site structure and navigation. Jira projects and service desk portals can be added and grouped into categories or sites that sit in the top navigation menu. Learn more on site organization.

Site Builder On-Premise:

On Refined Cloud, Jira projects work in a very similar way to Server. On Cloud and Server a Jira project home is a page you build up using sections and content modules in the inbuilt layout editor.

PAGE UNDER CONSTRUCTION

  • No labels