Need a Jira Cloud alternative to Behaviours / Initialisers to restrict field values based on logged‑

[bharath_bandari]

We are looking for a native Jira Cloud capability (or recommended approach) that works similar to Behaviours / Initialisers in Jira Cloud

We are not using ScriptRunner or any third‑party apps.
Use Case
We have a Customer Request Type with a custom field called Applications (single select).
Example field values:
MyCOTIVITI
Okta
Other

Requirement
When a request type is opened:
User A should only see “MyCOTIVITI”
User B should only see “Okta” and “Other”

The visible values must be restricted dynamically based on the logged‑in user (e.g., user, group, or role).
This restriction should apply:

On the request creation screen
Without changing issue types or workflows
Without external apps such as ScriptRunner

What We’ve Observed
Field Context Configuration allows static value control but does not support user‑based or dynamic value filtering.
Jira Automation can set field values after creation, but cannot restrict selectable options at form load.
Request type field configuration does not provide conditional visibility of specific field options per user.

Expected Behavior
Jira Cloud should provide a way (native or recommended workaround) to:
Dynamically control which field options are visible
Based on the logged‑in user, group, or role
Similar to Behaviours / Initialisers in Jira Server/DC

Actual Behavior
All users see all values of the Applications field, regardless of the logged‑in user.

Questions
Is there any native Jira Cloud feature that can achieve this?
Is this functionality on the product roadmap?
Are there any recommended best practices for achieving user‑based field value restriction without third‑party apps?

[Marc -Devoteam-]

HI @bharath_bandari 

You can start using assets and add users as objects in assrts, make sure the object also has an attribute of type usr, so you can link the asset to a real Jira user.

Then make sure to also add Applications as objects and on the user object, add a reference attribute so you can add Application object you have also created as objects in assets.

Then create a custom field of type Assets, where you will show the application objects from assets and use a filter to bas this on inbound or outbound user object.

The direction is based on how you have used the reference in Assets between User object and Applicaiton objects.

[mr john]

Hey! Unfortunately, Jira Cloud doesn’t currently support dynamic field option visibility based on user/group natively like Behaviours in Server/DC. Without apps, common workarounds are using separate request types or forms per user group, or handling it post-submission with automation.