- 
    Suggestion 
- 
    Resolution: Unresolved
- 
        7
- 
        36
- 
        
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
I'd like to be able to edit screens and show a field, yet not let it be editable. For example, I want to set a policy here that certain fields, once created, can never be changed (such as description and original estimate). Yet when editing a bug (or on other screens, like assign-to), I want those fields to still show up so the user has some context.
For implementation, I was thinking something really simple. The screen editor has a table with Position, Name, and Remove. This feature could be implemented by just adding another column of checkboxes after Name called Read-Only. Then the screen renderer can decide whether or not to make something editable by checking this flag.
Workaround
https://confluence.atlassian.com/display/CLOUDKB/Restrict+editing+of+a+custom+field+based+on+group
- is duplicated by
- 
                    JRACLOUD-7643 Display uneditable fields on workflow transition screens - Closed
 
- 
                    JRACLOUD-64330 Allow fields to be read only. - Closed
 
- 
                    JRACLOUD-77196 Allow field configuration to set read-only capabilities to sets of users. - Closed
 
- is related to
- 
                    JRACLOUD-35727 Add a new post function that make custom fields to be read only in workflow transitions - Gathering Interest
 
- 
                    JRACLOUD-61737 As an admin I would like to set permission for users editing the original time estimate - Gathering Interest
 
- 
                    JRASERVER-7475 Have ability to show read-only fields on screens - Gathering Interest
 
