Bug #102746 for RT-Extension-MandatoryOnTransition: on transition type, all custom fields are displayed instead of just the mandatory ones

Hey, We recently upgraded from RT 4.0.20 to 4.2.9. We were previously running version 0.04 of the MandatoryOnTransition extension. When we upgraded RT we also upgraded to the latest version 0.09 of the MandatoryOnTransition extension. We have noticed in the new version, all custom fields are displayed when we try to update the ticket with the mandatory transaction type I have tested with stalled and resolved and both do this. In version 0.04 only the mandatory fields showed up on the update page. (at least for resolve transitions, which is the only type we used so I never tested any other types) I believe this to be a bug since the README says: This RT extension enforces that certain fields have values before tickets are explicitly moved to or from specified statuses. If you list custom fields which must have a value before a ticket is resolved, those custom fields will automatically show up on the "Resolve" page. The reply/comment won't be allowed until a value is provided. Unless I am reading that wrong, only the custom fields which must have a value should automatically show up on the "Resolve" page. I have tested with RT version 4.2.10 as well, and we also upgraded MandatoryOnTransistion to 0.09_01 and the same thing happens. (I am very excited that 0.09_01 enforces status changes through the Basics tab so there is no way I would revert to an older version now) This is a screenshot of the custom fields listed on Resolve Page: /Ticket/Update.html?Action=Comment&DefaultStatus=resolved&id=4165 Only custom fields "CF Test -1", "CF Test - 2", and "CF Test -4" are mandatory on resolve, yet "CF Test - 3" still shows up. [cid:image001.png@01D05D8B.BD901C80] Here is the config we have setup: Set( %MandatoryOnTransition, 'Test Queue' => { '* -> resolved' => ['CF.CF Test - 1', 'CF.CF Test - 2', 'CF.CF Test - 4'], }, ); We have some production queues with more than 30 custom fields in them, and having all the custom fields show up ends up looking pretty messy, and makes it hard to find the custom fields that need to be filled in and have gotten some complaints from our users since the upgrade Thanks, Justin