Setting the behavior code made the custom field act different way.

Marija Ušakova April 6, 2018

Dear @Alexey Matveev

How to stop this from happening as i saved code, when clicking on the customfield the behavior changed it goes on to the pop-up upon click it on the view screen, and I'm confused as I cant edit on the view screen itself as we always do, is there a way to stop it.

 

 

1 answer

Suggest an answer

Log in or Sign up to answer
0 votes
Alexey Matveev
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 6, 2018

That is how scriprunner works. You can find it in sriptrunner documentation.

I ll try to ask somebody from Adaptivist and let you know. Or you can open a ticket in Adaptivist support .

Marija Ušakova April 6, 2018

Sure , can I ask why the behaviour code changes doesn't reflect in chrome, but it does reflect in safari?

Alexey Matveev
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 7, 2018

I do not have safari. I think you d better ask Adaptivist.

Alexey Matveev
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 8, 2018

Your question was why the edit screen pops up, when you begin to edit a field on the view screen, right?

Here is what is in the documentation
On the View Issue screen, trying to edit a field with a behaviour will launch the edit issue screen, instead of the normal inline editor.

It did not work like that in older versions, but in that case behaviours did not work at all, if you began to edit a field on the view screen. I guess, even if you somehow turn off the feature, your behaviours will not work on the view screen. I guess, that is how ScriptRunner works.

What do you mean that code changes does not reflect in chrome? Did you try to refresh the page with Ctrl+F5?

Sorry, I was not able to answer your questions because we had here a Java conference and I attended it.

Marija Ušakova April 9, 2018

No Problem @Alexey Matveev, I can wait. The code responsible for the text into the custom field works in safari but not in chrome, meaning the text that is editable and updatable on both screens when I use Safari browser. On the other hand it doesn't work at all in chrome as the edit screen in chrome always shows default value does not show updated values.

Alexey Matveev
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 9, 2018

What is your final script and what is your scriptrunner version?

Marija Ušakova April 10, 2018

Script runner version 5.3.5

 

Alexey Matveev
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 10, 2018

I think, you should open a ticket in ScriptRunner:

https://productsupport.adaptavist.com/servicedesk/customer/portal/2

TAGS
AUG Leaders

Atlassian Community Events