Behaviours plugin: losing required asterisks despite validating requiredness

Ashton Treadway

I have a workflow transition where a customer fills in several fields and submits it. Three of the fields are marked as required in the field configuration scheme, and pass through a scripted validation on the transition.

Any behaviour that checks requiredness seems to make the red asterisks disappear; whether it's simply a global behaviour that enables the two required checks, or a more targeted behaviour running against those fields.

Any ideas on what might be going on? I'm able to run other behaviours on the transition to hide certain fields, without losing the required asterisks, so it doesn't seem to be a problem with having more than one behaviour on the transition.

Still, like I said, as soon as I apply any kind of requiredness checking to either the transition as a whole or the fields specifically, I lose the red asterisks.

JamieA

Ashton, the red asterisks should disappear only when the field has a value. If the value is removed they should come back. Does that not happen?

This is not exactly the same behaviour as when using jira field configurations... I'll probably change it so that the asterisk stays even when the value is filled, to avoid confusion.