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
4,297,995
Community Members
 
Community Events
165
Community Groups

Why is behaviour running when form value hasn't changed.

I have behavior that is attached to a custom field (Client Type).  If the Client Type changes, I need to reset another custom field (State) to None so that the user has to pick it again.

This works fine while making changes to different fields on the form, but the behavior also runs when I submit the Create form and wipes out the other custom field so the form throws an error because the 2nd custom field is required and has been reset to None.

The value of the Client Type field did not change but the code is still running.  I have verified the through logging.

import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.issue.fields.CustomField
import com.atlassian.jira.component.ComponentAccessor
import org.apache.log4j.Level

log.debug("Running Client Type field code")

def ClientTypeField = getFieldById(getFieldChanged())
def selectedClientType = ClientTypeField.getValue().toString()
log.debug("Client Type = " + selectedClientType)

def stateField = getFieldByName("State")
stateField.setFormValue(null)

 

Why is the behavior running when I submit the form???

2 answers

Hi Margaret,

It's possible caused by this bug here: Field server-side behaviour scripts trigger when create/edit window opened before the user has interacted with the field

When you submit the form and an error message is thrown, it reload the screen and the field server-side behaviour scripts triggered before/without interacting with the field.

0 votes

That is not my experience...

What I normally see is that the script runs once when you open the screen (be that for create, edit or any transition) and the form is initialized with its starting value. FOr create that could be "null" or the default value for the context. For edit/transition, that would be with the value coming from the issue object in the back-end.

Then, it executes only when you change the value.

I've never seen it executing when submitting the form.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

117 views 1 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you