Conflict with Ticket Validator Plugin

[sdw_1979@…]

Hi, i've a TRAC 0.12 and i've installed your (great) plugin, it's ok and awesome but i've a problem with the option date_empty = true.

I've configured two date fields, due_assign and due_close, to identify the start and the finish of a ticket life, the due_close is made required by the TicketValidatorPlugin. When a ticket state become Closed , the due_close field becomes required.

The problem is that if i choose to use the option date_empty = true, i can leave an empty date even if the TicketValidatorPlugin is working and if i don't use the date_empty, the field is ALWAYS required and i don't want to insert an open date (31/12/9999) to force the validation, i want the user to insert a true date only AFTER the closing of the ticket.

I hope you understand my explaination, sorry for my english.

[Ryan J Ollos]

sdw_1979@…, I think that I understand your issue, and I have an interest in eventually using the DateFieldPlugin together with the TicketValidatorPlugin, so I wish to help resolve this issue. I will see if I can reproduce the issue in a development environment.

Please post a comment if you are still around and have still have an interest in this issue being resolved. I'd also appreciate if you can post your trac.ini configuration sections for both the DateFieldPlugin and TicketValidatorPlugin.

[Ryan J Ollos]

The forthcoming Trac 1.2 supports time fields, so this plugin is being deprecated.