I need to make a custom field read-only but visible on the edit screen. I see several related questions have been asked, but none are recent.
Is there a straightforward way in Jira to create a custom field and associate it with screens, and the user cannot edit the field when viewed on the issue edit screen?
I want to populate the value of the custom field via automation rather than have the user enter it on the issue screen.
It seems there should be a read-only option for custom fields. Has anyone solved this without using JavaScript or modifying the workflow?
Yes, assuming you have admin rights you can create a text read-only field.
ctrl+k -> custom fields. Create custom field and select the Advanced options
Paul, thanks for the tip! I think I can make this, just like they had a Numeric (read-only) custom field option.
Thanks for the assist!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @donhames , Welcome to the Community!
In addition to @Paul O 's suggestion, you could try this approach for adding other types of custom fields by adding them to the View Issue screen (the issue operation screen) and not adding them to the Edit operational screen (you would have to have separate Edit and View issue operation screens, of course!):
1. Go to Project settings > Screens and click the down arrow to display the Operation Screens for the applicable issue type.
2. Click the View issue screen link (e.g., "FINDEV Service Request View Issue Screen") and select the custom field to that screen using the drop-down list at the bottom.
3. Go to Project settings > Request types and open the request type related to the screen you need.
4. Click the Issue view tab to see the Issue view configuration screen (the Agent screen) and drag that field to the location on the screen where you want it (the field may be at the bottom of the "Hidden when empty fields"). Now it will be visible on the Issue View (Agent) screen but not editable.
You an open any existing ticket of that request type and verify it. And if you want to make that field editable in the future, you'd just need to add it to the Edit Issue Screen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am using this strategy in a JWM project. We are still able to edit the field in the list view. Any hints how we would prevent this or just keep the column hidden?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm, good question @Carla Norman! The only thing I can think of is to click the down arrow next to the column (field) name you want to remove and click Hide field. I'm an admin so that might be a requirement to do this, and I don't know if that affects everyone or just my view so you might try that and see if others can still see that column. If you come up with something better, please post here for us!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.