Selecting *no* trigger value (no 'not set', none of the allowed values) marks the field as 'controlled'
I'd expect this to have the same effect than when selecting 'not set' : I don't want this field to control the current field.

And the 'not set' option itself is not really clear, kind of confusing...

Comments

peterpoe’s picture

peterpoe commented
Category: bug » task
Status: Active » Postponed

Fixed the bug.

As for the interface issue, I'll look into it.

peterpoe’s picture

peterpoe commented
Status: Postponed » Fixed

Backported from d6 update.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.