Forums

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

Multiple script runner calls on browse issue

Madhu Kiran Yalamanchili
Contributor
April 20, 2018

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. 

2 answers

0 votes
Madhu Kiran Yalamanchili
Contributor
April 20, 2018

@Nic Brough -Adaptavist- thank you for your response. Do you think these calls triggered due to workflow validators? 

Nic Brough -Adaptavist-
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.
April 20, 2018

Absolutely not validators, those calls are all Behaviours.

Madhu Kiran Yalamanchili
Contributor
April 22, 2018

We dont have behavior module enabled on our instance. But still seeing behavior related calls.

 

Any help ?

Nic Brough -Adaptavist-
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.
April 23, 2018

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. 

Madhu Kiran Yalamanchili
Contributor
May 16, 2018

Disabling  "Behaviour inline edit issue assets" module in ScriptRunner plugin resolved this issue.

 

Thank You
Madhu

0 votes
Nic Brough -Adaptavist-
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.
April 20, 2018

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)

Madhu Kiran Yalamanchili
Contributor
April 20, 2018

@Nic Brough [Adaptavist] thank you for your response. Do you think these calls triggered due to workflow validators? 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events