Locking field editing after ticker creation

[Dilan Kaplan]

Hi all, 

There are two separate pages which have tried to answer this question however both are not the right solutions for me. I was hoping that maybe there was an update solution somebody could help me with.

I want to prevent certain fields from being edited after ticket creation - I have created pick list custom fields which I need to be locked after ticket creation for purposes of workflow conditions created to replicate an approval flow.

Currently any user is able to edit these fields but I would like to find a way these can be fixed after the ticket is created.

Any suggestions would be greatly appreciated

Best,

DK

[Earl McCutcheon · Accepted solution]

Hi Dilan,

Field level security is not something that exists natively in Jira and it is not something that will be added to the application, the reasoning for this decision is discussed in the status updates on following Feature request for this type of functionality, noting the request was created before jira cloud so it is filed under the Jira Server project but still applies to both platforms:

• https://jira.atlassian.com/browse/JRASERVER-1330

Also there are some workarounds noted:

Workarounds
Higher in the thread Erik S makes a comment about a workaround that may be useful for some users:
http://jira.atlassian.com/browse/JRA-1330?focusedCommentId=55032#action_55032
it is documented further here:
http://confluence.atlassian.com/pages/viewpage.action?pageId=149834
Third party commercial plugin:
https://plugins.atlassian.com/plugin/details/23216

We are going to close this issue, mark it as "Won't Fix". Any further options that we uncover will be noted on this issue.

Regards,
Earl

[Dilan Kaplan]

Thank-you Earl, 

Best,

DK