We should follow Hibernate's example (uggh) of assuming the property name matches the field name; we could then add field annotations to the search path for property annotations (that already includes searching the getter and the setter).
This would make Tapestry + Groovy that much nicer, as validation and other annotations could go directly on the fields.
|Field||Original Value||New Value|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Fix Version/s||5.0.12 [ 12313048 ]|
|Status||In Progress [ 3 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|
|Workflow||jira [ 12431551 ]||Default workflow, editable Closed status [ 12568751 ]|
|Workflow||Default workflow, editable Closed status [ 12568751 ]||jira [ 12590117 ]|