behavior and setError position

[Tim Nixon]

Here's our scenario:

A customfield (lets's call it "where found") that was not originally required now is required through a behavior

A user edits an issue, but uses a custom view to see only the few fields they care about.

They do NOT select the field "Where found" in their custom edit-view

The field is blank since the issue is old.

They edit and submit and nothing happens.. since the Where found field is not on the custom view the message that the field is required is at the bottom and they did not know to scroll down to see the message. I added a second behavior to add another message but it also displays the message at the bottom.

Since I cannot know what fields are actually on the custom edit-view how do I make sure the message is visible to the user?

Thanks