Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

201 views 1 6
Read article

Atlassian Community Events