Once the issue is created, the custom field cannot be changed

[kalaimani]

Hi Team

It is Kanban Board and Company Managed project 

I have two custom date fields that are automatically populated when a ticket is created. After that, no one should be able to change these fields. How can I achieve this without modifying the Edit screen? Since my screen issue type is set to default, is there a way to do this through conditions or automation?

[Ravina · Accepted solution]

Hi @kalaimani By default Jira cloud does not have field level security that you can allow to edit the certain custom fields to some group/role, there are some marketplace apps that offers this functionality. this is not something can be achieved using workflow advance functionality like conditions, validators, post-function, etc or automation.

https://marketplace.atlassian.com/apps/1226365/secure-custom-fields-security-permission-for-jira?tab=overview&hosting=cloud

There is an option ticket on Atlassian for this functionality that you can follow to get the future updates

https://jira.atlassian.com/browse/JRACLOUD-72022

You mentioned that you don't want to modify the screens but as this is not possible by default and want to check if updating the screens then you can follow this related post if you want to configure this using screens.

https://community.atlassian.com/t5/Jira-Service-Management/Configure-field-security-permission/qaq-p/1510539

[kalaimani]

Thanks @Ravina i will try with screens.

[kalaimani]

Hi @Ravina 

Thank you. I created a separate screen for Edit and removed the custom fields I didn't need. It works now.

Thanks Again!!

[Rudy Holtkamp]

Hi @kalaimani ,

You can create a read-only text field, which you populate/change via an automation rule.

Create it as a Text Field (read-only) custom field, which is available as an Advanced field type