| 1 | | 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". |
| 2 | | 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 a plugin ([http://trac-hacks.org/wiki/TicketValidatorPlugin]) so when a ticket state become "Closed" , the "due_close" field becomes required. |
| 3 | | The problem is that if i choose to use the option "date_empty = true" , i can leave an empty date even if the ValidatorPlugin 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. |
| | 1 | 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`. |
| | 2 | |
| | 3 | 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. |
| | 4 | |
| | 5 | 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. |
| | 6 | |
