...
Rw ui expands macro | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The way that Refined is built, a space can only exist in one site and category. You can however add a link to the space anywhere in the category menu, even if the space belongs to a different site.
This can be done from the Confluence admin UI:
Note that content placed in additionally created Refined Sites (so not the global one) will still render with the Refined theme set for that Site. To revert these space themes the space needs to be moved to the global site or the uncategorized uncategorised section. See our tutorials on this particular hybrid setup here:Use Refined only on specific sites and spacesTutorial: Keep original Confluence on one site and Refined for Confluence on other sites
The Refined Layout Space is a required component to ensure the Landing pages, Space Layouts and User Dashboards work as intended. For these Layouts it’s possible to add macros and attachments to be displayed. In order to render these as on any regular page there needs to be a Space & page to render it in. This is the purpose of the Layout space, which will internally create temporary pages when editing layouts. Under normal circumstances you’d never need to interact with this space, which is why it is archived and hidden from the regular places where you’d list spaces.
In most cases the key is setup as If for whatever reason that key was taken when the space was created, it might live under a different key. In that case you can find it by:
If you can't delete a category, there is probably spaces belonging to that category that you are not an admin for. You'll first need to find out what space is in the category by viewing the category menu on the site. Once you've found the spaces belong to the category, you'll need to be added as an admin to those spaces.
Refined for Confluence Server supports the following languages:
Refined follows Atlassian’s supported platforms. When using the administrative tools included with Refined, such as Site Builder, Theme Editor, or Space Layout editor we recommend using Chrome, Edge or Firefox.
It could be that one of the following issues occurred. For more background on this special space and its usage, see the FAQ item What is the Refined Layout Space (rwlayoutkey)? License issuesGo to General Configuration > License Details to see if your Confluence license has expired or if there are too many users on the license. Permissions on the Refined Layout Space - A change of user groupsSymptom: The main or category dashboard can't be edited. When clicking a module to open up the Confluence editor, you get a popup saying that you are not permitted to perform this operation, or you see a spinning “loading” icon. Cause: The user trying to edit the dashboard is not a member of the required user groups. Resolution:
|
Rw expand | ||
---|---|---|
|
Info |
---|
This issue is fixed in version 6.1.11. Upgrade to this version or a higher version to solve this issue, or manually enable the modules as instructed below |
You may need to manually enable the modules as instructed below, but making sure you are on version 6.1.11 or higher will fix the issue for when you restart Confluence in the future.
Symptoms
After upgrading to Confluence 7 and while using Refined version 6.1.7 to 6.1.10, there is a license banner visible on pages stating that you do not have a valid license.
Cause
Resources within Confluence are not made available in the order necessary for Refined app to function properly, and all modules in Refined are not enabled.
Solution
Go to manage apps.
Click Refined for Confluence.
Enable all modules.
Rw expand | ||
---|---|---|
|
This issue can happen due to migration or URL issues:
Migration
You have migrated from one server to another and the Refined folder was not moved correctly which means the images in the folder will not show up.
Make sure you have moved the Refined folder in Confluence home.
Make sure that the Confluence user has access to that folder on the server.
Base URL
You have changed base URL and need to resave the theme.
Make sure the base URL is set to the URL from which you are accessing your instance. Read Atlassian’s article about Configuring the Server Base URL.
Resave the theme: Go to Refined Administration > Themes > Hover the theme and click edit.
Without making any changes, click save.
Rw expand | ||
---|---|---|
|
Users can create and view Jira issues directly on your Refined sites. See below which default and custom fields we support – we continually add support for newly introduced fields.
Default fields
Field | Issue View | Issue Create | Issue Transition |
aggregateprogress | No | No | No |
affectedservices | No | No | No |
assignee | Yes | Yes | Yes |
attachment | Yes | Yes | Yes |
comment | Yes | Yes | Yes |
components | Yes | Yes | Yes |
description | Yes | Yes | Yes |
duedate | Yes | Yes | Yes |
environment | Yes | Yes | Yes |
fixVersions | Yes | Yes | Yes |
issuelinks | Yes | Yes | Yes |
issuetype | Yes, but not editable | Yes, but not editable | Yes, but not editable |
labels | Yes | Yes | Yes |
lastViewed | Yes | - | - |
parent (Next gen project) | Yes, but not editable | Yes | No |
priority | Yes | Yes | Yes |
progress | No | No | No |
project | Not editable | Not editable | Not editable |
reporter | Yes, but not editable | Not editable | Not editable |
resolution | Yes, but not editable | Yes | Yes |
resolutiondate | Yes, but not editable | No | No |
security | Yes | Yes | Yes |
summary | Yes | Yes | Yes |
textarea | Yes | Yes | Yes |
timetracking (timeestimate, timeoriginalestimate, aggregatetimeestimate, aggregatetimeoriginalestimate) | Yes, but not editable | Yes | Yes |
versions | Yes | Yes | Yes |
watches | Yes | No | No |
worklog | No | No | No |
workratio | No | No | No |
Custom fields
Custom field | Type | Issue View | Issue Create | Issue Transition |
com.atlassian.jira.plugin.system.customfieldtypes:cascadingselect | option-with-child | Yes, but not editable | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:datepicker | datepicker | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:datetime | datetime | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:float | number | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:labels | array | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes | array | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker | multiuserpicker | Yes, but not editable | No | No |
com.atlassian.jira.plugin.system.customfieldtypes:multiversion | array | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons | option | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:select | option | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:textarea | string | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:textfield | string | Yes | Yes | Yes |
com.atlassian.jira.plugin.system.customfieldtypes:url | string | Yes | Yes | Yes |
com.atlassian.jpo:jpo-custom-field-parent - Parent Link | any | No | No | No |
com.atlassian.servicedesk:sd-customer-organizations - Organizations | array | No | No | No |
com.pyxis.greenhopper.jira:gh-epic-label - Epic Label: | string | Yes | Yes | Yes |
com.pyxis.greenhopper.jira:gh-epic-link - Epic Link: | any | Yes | Yes | Yes |
com.pyxis.greenhopper.jira:gh-lexo-rank - Rank | any | No | No | No |
com.pyxis.greenhopper.jira:gh-sprint | - | No | No | No |
sd-request-lang com.atlassian.servicedesk.servicedesk-lingo-integration-plugin:sd-request-language | sd-request-lang | No | No | No |
type:number | number | Yes | Yes | Yes |
...
Rw ui expands macro | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Use the Atlassian license cost calculator to add Refined and based on your user count. Please note that apps are based on number of users and not agents, which means that for a JSM set up the price might vary.
All Refined sales are handled via Atlassian Marketplace. You can pay or get a quote directly through your my.atlassian.com account.
The Atlassian license tier determines the Refined license type you need. For example, if you want to install Refined for Confluence with a 100 user Confluence license, then you need to purchase a 100 user license of Refined for Confluence. The right tier is selected automatically in the Atlassian Marketplace.
Please read the related Atlassian documentation.
The license system is built by Atlassian. They give the following answer: "Marketplace app customers can get developer licenses for apps just as they can for host Atlassian products. Developer licenses are intended for staging or development environments only. Customers who have purchased Marketplace apps can get developer licenses by clicking the View Developer License link from their license page on my.atlassian.com. The license types between the app and host application must match. That is, an app with a developer license only works in a host application that also has a developer license. The same applies to production licenses—a host application with a production license only takes apps that also have production licenses. If an app license type doesn't match its host application, the Universal Plugin Manager reports a license error status of "Incompatible with product license (wrong type)" for that app. How to create developer licenses
You can evaluate Refined apps from the Marketplace for a longer time if needed. Atlassian manages licenses and trial extensions of Marketplace apps. Log into your my.atlassian.com account and extend the trial period. You can extend the trial up to 180 days (6x 30 days), read more on our Marketplace listing. |
...