How to make Group picker(Single group) field is read only in JIRA cloud

[Pavan kumar Mamidipaka]

How to make Group picker(Single group) field is read only in JIRA cloud

[Komal Santosh Sudulwar]

Hi,

In Jira Cloud, there isn't a native option to make a Group Picker (Single Group) custom field read-only while keeping it visible on the issue. Jira Cloud does not currently support field-level read-only permissions.

Depending on your requirement, you could consider one of these approaches:

If the field should only be populated during issue creation, include it on the Create screen and remove it from the Edit screen so it cannot be modified afterward.

If the field is only required during a workflow step, add it to a transition screen instead of the Edit screen.

If you need to prevent changes after the field is set, Jira Automation can be used to detect and revert unauthorized updates, although this doesn't make the field truly read-only.

If you require true read-only behavior based on users, roles, or conditions, you'll need a Marketplace app such as ScriptRunner or similar field-behavior extensions.

If you could share your specific use case (for example, who should be prevented from editing the field and at which stage), I'd be happy to suggest the most suitable approach.

[Pavan kumar Mamidipaka]

@Komal Santosh Sudulwar ,
I am following that way only but it's not working 

[Komal Santosh Sudulwar]

@Pavan kumar Mamidipaka 

Have you tried using ScriptRunner or similar field-behavior extensions?

If you can describe your specific requirement (for example, who should be restricted from editing the field and when), that would be helpful to find out the solution.

[Vinayak Wagh]

Hi,

I'm looking for the best approach to make a Group Picker (Single Group) custom field read-only in Jira Cloud.

As far as I know, there isn’t a way to make any particular custom field Read Only by default in Jira Cloud. One thing that comes to mind could be to use workflow transition screens where the field can be editable at certain transitions only.

Has anyone implemented a clean, native solution for this in Jira Cloud, or is using Marketplace apps the recommended approach?

I'd appreciate hearing about your experience and best practices. Thanks!

[Sean Button]

how will it be set? maybe you could place it on the view screen but not on the edit screen for the space in question. this way it's not editable on the issue but perhaps as you suggested on editable on create, transition etc?