Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Web Console is flooded with [SR Behaviours] messages

Alexey Suslin May 10, 2018

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?

1 answer

1 accepted

1 vote
Answer accepted
Deleted user May 10, 2018

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

Alexey Suslin May 10, 2018

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.

Deleted user May 10, 2018

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

sbhutada
Contributor
January 10, 2019

@[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 -

https://community.atlassian.com/t5/Jira-questions/Web-Console-is-flooded-with-SR-Behaviours-messages/qaq-p/978352#M313852

Please give your inputs.

Teja
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 21, 2019

@[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     

sbhutada
Contributor
March 21, 2019

@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.

Teja
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 22, 2019

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 

Suggest an answer

Log in or Sign up to answer