I have one customfield which I want to set read only in one of the workflow step. I am using scriptrunner behaviour for that. But every time when I click on edit button when I an in IMPLEMENTING status I see a lot of messages on console -
[SR Behaviours] Unrecognised backend ID, or possibly field with no available options: customfield_13911
[SR Behaviours] Unrecognised backend ID, or possibly field with no available options: customfield_13911
[SR Behaviours] Unrecognised backend ID, or possibly field with no available options: customfield_13911
I checked this solution - https://community.atlassian.com/t5/Jira-questions/Web-Console-is-flooded-with-SR-Behaviours-messages/qaq-p/793311. But this is not helping in my case.
Please let me know if this is behaviour bug or I am doing something wrong?
Below is the configuration I did in behaviours -
This issue is caused by a known bug in ScriptRunner versions prior to 5.4.42.
Bug ref:
https://productsupport.adaptavist.com/browse/SRJIRA-2949
Any users experiencing this issue should upgrade to at least Scriptrunner 5.4.42 or later.
Note: You may also see the same error in the browsers developer tools console log if the field does not exist on the transition screen which you have configured the behaviour to act on. However, I would not expect it to be a flood of messages.
In this case, you can code the behaviour scripts in a way that prevents them performing actions on fields that do not exist. For example, you could check the field object is not null before trying to set its properties such as if it is a required field.
Hi Sameer
This question is currently being investigated through our Support Portal.
I will post an update here when the support ticket has been resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.