I've got 3 fields that I want to be readonly and mark them in behaviour as readonly
however on any transaction screen (where there are no such fields) I got lots of messages in web console:
[SR Behaviours] Unrecognised backend ID, or possibly field with no available options: customfield_13322
[SR Behaviours] Unrecognised backend ID, or possibly field with no available options: customfield_13323
[SR Behaviours] Unrecognised backend ID, or possibly field with no available options: customfield_13321
... etc
Is there any way to not show them?
Hi @Alexey Suslin,
As the behavior configuration is associated to project, issue type and workflow it will validate the script during any action that is performed.
If you are looking for ignoring these three field related configurations then try to trigger the script only when getActionName()=="" so that it would skip the transitions.
Please let me know if you need further information.
Regards,
Priyanka
Actually, I have to do the opposite, ignore triggering that field on certain transitions, where those fields are not presented. (as I still need those fields to be read-only when open edit issue screen)
Probably I have to create a feature-request to Adaptavist, no sense to flood web console every second with the message that field is not found.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alexey Suslin,
Yes, whatever you said is true. I was under the impression that you are trying to skip all the transitions. If it's only for few transitions then we can specifically mention the action names.
Regarding inline edit, there is already a request that is available https://jamieechlin.atlassian.net/browse/JBHV-185 requesting for the same functionality.
Regards,
Priyanka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@[deleted] @Alexey Suslin
I have the same issue going on. The solution which you mentioned here is not helping at all. I have posted the question here -
Please give your inputs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@[deleted] @Alexey Suslin @sbhutada
We also have the same issue, web console overwhelmed with [SR Behaviours] Unrecognised backend ID, or possibly field with no available options: customfield_13609. Has anyone got the solution?
Best.
Tejas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Tejas Naik I had a hard time to resolve this issue.
In behavior, you are running a code or possibly doing getfieldbyname('XX') for a field which does on exist on Create or Edit screen that's where you run into this error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @sbhutada I have that fields on Create, Edit and as well as on transition screen. Still do not know why I am getting [SR Behavior] Unrecognized message. But I do notice all listed custom fields in the console are read-only fields in the Behavior section.
Regards
Tejas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.