Custom field not to be changed (read-only)

[Radosveta Delcheva]

Hi all, I would like to have a custom field that can not be changed. I've tried many of the available solutions online and it did not work for me. I would not like an add-on. One of the solutions was not to add the custom field to the edit screen, but view/edit screen are together, I've tried to split the screens, but then the field is not visible at all - it has default value in it, this is not the reason. It is not associated with the edit screen, but when I click edit in the ticket I can see it and select it, but after that is not visible in the ticket,. Do you have another idea? Many thanks in advance! Kind regards

[Nic Brough -Adaptavist- · Accepted solution]

You need to get the screens set up correctly.

You say:

"One of the solutions was not to add the custom field to the edit screen"

Correct - if you place it on create and view only, the user can put it in when the issue is created and it won't be editable later.

> "but view/edit screen are together, I've tried to split the screens"

Why can't you split them?  If the view and edit screens are currently set the same, then copy that screen to a new version, and associate it in the issue type screen scheme.  Then remove the field from the screen you use for edit

[Radosveta Delcheva]

Hi Nic,

Thanks for the advice how to split the screens, I've done it and now it works, what I have to say is that it is not an user friendly solution. I don't see the point to have the view and the edit screen as a single option and if you need some function to be executed to have to split them, associate, configure additionaly the custom field, etc.

One more time thank you for the quick reply and for the help, highly appreciated.

The support is incredible, just the functionality is not very optimal to use.

[Nic Brough -Adaptavist-]

I find it quite complex, but over the years have learned a couple of things

• it's very powerful, but that causes complex admin.  I'd love to see it simplified, but I've not come up with a good idea on a way to re-arrange it better
• Atlassian are not very good at picking defaults, which confuses and confounds things that really ought to be simple.  The worst one is the "everyone who can log in automatically gets into all the projects".  If they had picked a useful default, this communities top question would not be "how do I restrict users to a project" (answer - undo all the dreadful defaults and set it up properly).  The "shared view/edit screen" is another poor default - I would have created separate screens, even though they might well be identical, just to make it clear!

[Radosveta Delcheva]

Hi again and thanks for that insight too.

I am aware you can not expect many various actions and simplicity at the same time, that was meant not as a complaint, but  as an area of improvement. Would be great in case Atlassian tries to get those defaults more easy to use.

Thank you!

[Joe Pitt]

I'm confused. You say it has a default value, but not visible on the view screen. That shouldn't happen since it has a default value it should always appear.  

[Radosveta Delcheva]

Yes, but it does not have a view screen associated, only default and create and resolve.

I am confused as well