Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


ScriptRunner: Behaviour too late

Hi all,

We created a Behaviour for our Service Desk "Create Request" form that populates some read-only fields based on the content entered in a text field.

The problem is that if the end-user enters a value to the text field then clicks directly on 'Create', the "create" request is sent to the server before the read-only fields are updated.

We can see that the Behaviour is executed because the fields are updated before the screen transitions, but it's as if the browser didn't wait for the Behaviour to complete execution before firing the "create" request.

This causes an immediate problem for when the read-only fields were initially empty, as they're mandatory. The "create" request is refused saying that these fields must be filled, which is confusing since the user sees values in them.

But it can get worse if the end-user modifies the text field after having entered something valid. The request could actually be created with the wrong, previous values.

Currently, my workaround is to inject Javascript to disable the "Create" button until there's a value in one of the read-only fields, but this won't solve the "wrong value" problem.

Any ideas on how to solve this pickle?


0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events