Product questions
...
| Rw expand | ||
|---|---|---|
|
If a project is missing from the Site Builder, the most probable cause is that you're not an administrator of that project. Check the project permissions to make sure you're an administrator.
| Rw expand | ||
|---|---|---|
|
Refined for Jira Server/DC works with both standalone Jira Core/Software instances, as well as with Jira Service Management.
If you’ve been using Refined with Jira Core/Software and then install Jira Service Management, you need re-install the Refined app. Your previous data is retained and the reinstall will allow the app to properly prepare all the needed resources. In some cases you might need to restart Jira.
| Rw expand | ||
|---|---|---|
|
Sometimes when Jira starts up, the resources needed for Refined app to enable haven't been loaded yet. In these situations Refined remains disabled. In most cases restarting Jira will solve the issue.
| 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 Jira home.
Make sure that the Jira 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 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
...
Supported when viewing an issue
...
Supported when creating an issue
...
aggregateprogress
...
No
...
No
...
assignee
...
Yes
...
Yes
...
attachment
...
Yes
...
Yes
...
comment
...
Yes
...
Yes
...
components
...
Yes
...
Yes
...
description
...
Yes
...
Yes
...
duedate
...
Yes
...
Yes
...
environment
...
Yes
...
Yes
...
fixVersions
...
Yes
...
Yes
...
issuelinks
...
Yes
...
Yes
...
issuetype
...
Yes, but not editable
...
Yes, but not editable
...
labels
...
Yes
...
Yes
...
lastViewed
...
Yes
...
-
...
priority
...
Yes
...
Yes
...
progress
...
No
...
No
...
project
...
Not editable
...
Not editable
...
reporter
...
Yes, but not editable
...
Not editable
...
resolution
...
Yes, but not editable
...
Yes
...
resolutiondate
...
Yes, but not editable
...
No
...
summary
...
Yes
...
Yes
...
textarea
...
Yes
...
Yes
...
timetracking
...
No
...
No
...
versions
...
Yes
...
Yes
...
watches
...
Yes
...
No
...
worklog
...
No
...
No
...
workratio
...
No
...
No
Custom fields
...
Field
...
Type
...
Supported when viewing an issue
...
Supported when creating an issue
...
com.atlassian.jira.plugin.system.customfieldtypes:cascadingselect
...
option-with-child
...
No
...
No
...
com.atlassian.jira.plugin.system.customfieldtypes:datepicker
...
datepicker
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:datetime
...
datetime
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:float
...
number
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:labels
...
array
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes
...
array
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker
...
multiuserpicker
...
Yes, but not editable
...
No
...
com.atlassian.jira.plugin.system.customfieldtypes:multiversion
...
array
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons
...
option
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:select
...
option
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:textarea
...
string
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:textfield
...
string
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:url
...
string
...
Yes
...
Yes
...
com.atlassian.jpo:jpo-custom-field-parent - Parent Link
...
any
...
No
...
No
...
com.atlassian.servicedesk:sd-customer-organizations - Organizations
...
array
...
No
...
No
...
com.pyxis.greenhopper.jira:gh-epic-link - Epic Link:
...
string
...
Yes
...
Yes
...
com.pyxis.greenhopper.jira:gh-lexo-rank - Rank
...
any
...
No
...
No
...
com.pyxis.greenhopper.jira:gh-sprint
...
No
...
No
...
sd-request-lang com.atlassian.servicedesk.servicedesk-lingo-integration-plugin:sd-request-language
...
sd-request-lang
...
No
...
No
Licensing and pricing questions
...
| Rw expand | ||
|---|---|---|
|
Use the Atlassian license cost calculator to add Refined and based on your user count: https://www.atlassian.com/software/pricing-calculator
Licensing and pricing
| Expand | ||
|---|---|---|
| ||
For trial and pricing information, please see our Atlassian Marketplace listing. 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 from what you get here. Example:  rw- |
| Expand | ||
|---|---|---|
| ||
All Refined sales are handled via Atlassian Marketplace. You can pay or get a quote directly through your my.atlassian.com account.rw- |
| Expand | |||
|---|---|---|---|
| How do I know which license to choose when purchasing Refined
| ||
The Atlassian license tier determines what the Refined license type you need to buy for Refined. E.g. if you are installing Refined on Confluence . For example, if you want to install Refined for Jira Service Management (JSM) with a 100 user Confluence Jira license, then you need to purchase a 100 user license of Refined for Confluence Server. This is done automatically via JSM. The right tier is selected automatically in the Atlassian Marketplace. rw- |
| Expand | |||||||
|---|---|---|---|---|---|---|---|
| I have a non-profit/community license. Why haven't my licenses been merged to a my.atlassian.com account?|||||||
| Rw expand | title |
| |||||
The license system is built by Atlassian and here is their answer regarding a developer license. 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.” Read more: How to create developer licenses rw- |
| Expand | ||
|---|---|---|
| ||
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. This is how it works across hostings: Server YouYou can extend the trial up to 180 days (6x 30 days) . Read, read more on our Marketplace listing. |
Product
| Expand | ||
|---|---|---|
| ||
You can still use our Server apps after February 16, 2024. However, we’ll not publish any new versions and we don’t offer support or maintenance. We encourage our Server customers to migrate to Data Center
Cloud
|
...
or to Cloud instead, where we will continue to release updates and offer support. |
| Expand | ||
|---|---|---|
| ||
If a project is missing from the Site Builder, the most probable cause is that you're not an administrator of that project. Check the project permissions to make sure you're an administrator. |
| Expand | ||
|---|---|---|
| ||
Jira Service Management Server/DC works with both standalone Jira Core/Software instances, as well as with Jira Service Management. If you’ve been using Refined with Jira Core/Software and then install Jira Service Management, you need re-install the Refined app. Your previous data is retained and the reinstall will allow the app to properly prepare all the needed resources. In some cases you might need to restart Jira. |
| Expand | ||
|---|---|---|
| ||
Sometimes when Jira starts up, the resources needed for Refined app to enable haven't been loaded yet. In these situations Refined remains disabled. In most cases restarting Jira will solve the issue. |
| Expand | ||
|---|---|---|
| ||
This issue can happen due to migration or URL issues: Migration
Base URL
|