Hello Team,
We are seeing multiple scriptrunner calls for each browse action. We are not sure why these calls are triggered.
Plugin Version: 5.3.7
For single Jira action there are almost 11 rest calls..
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513895 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513905 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513911 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513920 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513935 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513952 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513942 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513960 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513966 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513978 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215513972 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
/rest/scriptrunner/behaviours/latest/validators.json?issueId=2829083&_=1524215514040 40 no-cache, no-store, no-transform application/json;charset=UTF-8 chrome:6736
Can someone please let us know why there are many rest calls.
@Nic Brough -Adaptavist- thank you for your response. Do you think these calls triggered due to workflow validators?
Absolutely not validators, those calls are all Behaviours.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We dont have behavior module enabled on our instance. But still seeing behavior related calls.
Any help ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Disabling behaviours stops the code running, but it can't stop the core looking for the code being called.
Re-enable Behaviours, and then delete all the Behaviours you have defined, then disable it again. That will minimise the number of calls made.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Disabling "Behaviour inline edit issue assets" module in ScriptRunner plugin resolved this issue.
Thank You
Madhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's because Jira makes multiple requests to its own functions (which Behaviours hooks into).
I've never had a good explanation from Atlassian why Jira does this, but it is endemic.
When you're writing stuff for Jira, you have to assume a lot of your code is going to get run multiple times for any single action, especially the issue view (validators, post-functions and listeners are the exception)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough [Adaptavist] thank you for your response. Do you think these calls triggered due to workflow validators?
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.