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

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

 

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./

Status

Assignee

JamieA

Reporter

JamieA

Internal Complexity

Unknown

Internal Value

Unknown

Components

Priority

Major