We're updating the issue view to help you get more done. 

disable jira's dirty form checking for fields that have been set through behaviour setValue

Description

*This issue has moved*

This issue has been moved permanently to Adaptavist's Product Support JIRA instance.

All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the
Can't access your account link in order to reset to a new password.

Either the value has been set on load, in which case it's not significant, or it has been set through modifying other fields, in which case their "dirty" property will kick in.

So it's probably OK to set the saved initial value to the same as the "set" value./

Environment

None

Status

Assignee

JamieA

Reporter

JamieA

Internal Complexity

Unknown

Internal Value

Unknown

Components

Priority

Major