---
title: "Live Fields limitations on Jira Service Management customer portal"
canonical: "https://support.appfire.com/space/PSJ/3265232989/Live%20Fields%20limitations%20on%20Jira%20Service%20Management%20customer%20portal"
format: markdown
---
> Macro (aura-html)

## Summary

Some Jira Service Management (JSM) customer portal fields use Atlassian's React-based components. As a result, certain Live Fields behaviors might not work as expected on the portal.

This limitation can affect functionality such as:

- Dynamically setting field values.
- Listening to field value changes.
- Restricting select options.
- Hiding or disabling fields.
- Displaying contextual helper messages.

The issue primarily impacts select list fields and other uplifted portal components introduced in newer Jira Service Management versions.

## Why this happens

Live Fields historically interacted with portal fields through standard browser DOM APIs and JavaScript event listeners.

With the newer React-based field implementation:

- React manages field state internally.
- External DOM changes can be overwritten during component rerenders.
- Some browser event listeners no longer behave consistently.

As a result, some dynamic field interactions previously supported by Live Fields might stop working or behave unpredictably.

## Workaround

Atlassian currently provides a dark feature that restores the previous non-React select implementation.

### Enable the workaround

1. Open the following page in your Jira instance:
2. Add the following dark feature:
3. Clear the browser cache, if necessary.
4. Reload the customer portal page.

## Important limitations of the workaround

Review the following limitations before enabling the workaround:

- It is an Atlassian internal dark feature.
- It is not a permanent public API or supported integration mechanism.
- Atlassian can remove or change the feature in future releases.
- Disabling the uplift also disables the accessibility improvements introduced by the new components.
- The workaround applies instance-wide.

Because of these limitations, treat the workaround as temporary.

## Current status

We are discussing this limitation with Atlassian and advocating for a supported public API for interacting with customer portal fields in the new React-based architecture.