...
If you have any questions, please contact us.
After adding aJira Software project/projectsJSM project, users can create and view issues/ requests directly on your Refined sites. See below which default and custom fields we support and which ones have limitations. We continually add support for newly introduced fields.
| Table of Contents |
|---|
Jira Software issue 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
...
Yes
...
Yes
...
com.atlassian.jira.plugin.system.customfieldtypes:userpicker
...
user
...
Yes, but not editable
...
Yes
...
Yes
...
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
...
.
...
-
...
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
JSM request fields
We support most JSM request fields, with limitations for the ones listed below. We continually add support for newly introduced fields.
Forms and Assets fields
Due to Atlassian APIs, we are currently unable to support fields for Forms (previously called ProForma) and Assets (previously called Insights). We are in direct contact with Atlassian regarding this. You’re welcome to vote/comment on these active Atlassian tickets:
Affected Services fields
Due to Atlassian APIs, we currently do not render this field on Refined because the field does not return any values (ie. the field is not functional). As a result, we do not display the field. We are in direct contact with Atlassian regarding this. You’re welcome to vote/comment on this active Atlassian ticket:
...
If this is a mandatory field, we suggest that it’s set to optional. Otherwise, requests cannot be created via Refined.
Hidden Summary fields and preset values
If a request type has a Hidden Summary field and a preset value, we are not able to display that value on Refined in the request view. This happens because the Atlassian API doesn’t return that value to us. You’re welcome to vote/comment on this active ticket on Atlassian.
Assignee field
Only users with a Jira Software license can see the assignee: it is not visible to JSM customers.