From ScriptRunner Behaviour we set a multi-select Assets field read-only depending on user role etc but it is still possible to remove values (not add though). It is not like this if I deselect the "Multiple" option in the configuration for the field. Why is this? How do I make the field read-only so that no values can be removed?
AdaptaVist Group support was able to reproduce our problem and consider it a bug. After upgrade to the latest version, 9.29, they are no longer able reproduce it. Looking at release notes, I see that the bug was fixed in 9.26, mentioning read-only fields in general.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure if I got all the parameters right when I submitted the question but we are on Jira Data Center with:
Jira Software 10.3.12 Adaptavist ScriptRunner for JIRA 9.24.0
We set the Assets field read-only from the initialiser in our Behaviour for the Bug issue type using:
cfIncludeInMR.setReadOnly(true)
The code around is not important, we simply check the user's role to decide if we want to set the field read-only or not. We can see that the field gets read-only (grey background) but still it is possible to remove (not add) values if the Assets field is configured for multi-select (otherwise not).
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.