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 5 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.

On Refined for Jira Server DC you can pull and display content from Jira and Jira Service Desk on your Refined customer facing portal/help center. If you’ve connected a Confluence instance, you can display knowledge base articles from as many Confluence spaces as you wish.

Refined will display knowledge base articles in-frame. Learn how to configure knowledge base settings.

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.

Site Builder on Cloud

  • Think of Refined as a CMS or website content builder for Atlassian Tools. The site builder is where the majority of the site configuration is done.

  • Use the site builder to organize the site structure and navigation. Once the data sources are activated, you can add Jira, Jira Service Desk portals and Confluence spaces to a site using the plus symbol. Learn more on the site organization.

Site Builder On-Premise:

  • Similar to Cloud, Refined can be thought of as a CMS builder for Atlassian tools. Like on Cloud, the site builder is where the majority of the site configuration is done.

  • Use the site builder to organize the site structure, navigation and view permissions. Any existing JSD projects will automatically be in the site builder on the Global JSD Site. Jira projects can be added to a site using the plus symbol.

  • Rearrange the Jira projects and JSD portals into categories and/or sites.

  • Navigate to sites using the top hamburger menu.

  • Navigate to categories from the top navigation menu (as breadcrumb or dropdown menu). Learn more on site organization.

  • Permissions need to be configured on native Jira. It’s not yet possible to add additional site or category permissions (but this is on the roadmap).

  • Permissions from native Jira and Jira Service Desk will be honored, and additional permissions can be added to sites and categories. More on this below.

PAGE UNDER CONSTRUCTION

  • No labels