doesn't work on custom ticket field

[anonymous]

Hey, cool plugin.

Got it to work for milestones, although it defaults to MM/DD/YY, trac default for Milestones is MM/DD/YYYY. added duedate=MM/DD/YYYY seem good.

I have a custom field called due_close, can't get it to work with, tried the following: due_close=MM/dd/YY

• field-due_close=MM/dd/YY
• "due_close"=MM/dd/YYYY
• Due Date=MM/DD/yy
  • (that's the label, btw)

and a few other combos.

Anyway, thanks for the plugin, hope to see the kinks worked out, it's a long needed feature. Might want to up date the wiki page regarding the custom fields. You have

For e.g. in the ticketsystem, you have an field called YYYY/mm/dd, if you now click on ....

which might be part of my issue, I don't know actaully what your field is called. I assume field-due_date, or is it just due_date, and field is a special prefix for your plugin.

anyway, again, thanks

[anonymous]

Hi,

thank you for the report. To check the exact error, could you please please go to the milestones site and save it completly (with all images, scripts etc), pack it with anythin you like and attache it to this ticket. That way, I could have a look into it.

Best regards,

jjbig

[anonymous]

Replying to jjbig: I guess, the milestones section works fine. It's a ticket field that doesn't, so I am not sure what you're asking for here. Still not sure if the field- in your field-due_close is part of your custom field name, in your examples on the hack wiki.

[jjbig]

I expanded the Wiki a litle bit. The first wiki page was gernerated automaticaly and I never checked. Sorry. Could you give me any feedback, wether the new howto is working for you and understandable?

[anonymous]

yep, like a giant light-bulb. I needed to add the files=milestone_edit.html,ticket.html

Thanks again. And again, very awesome plugin. Since I require dates for my project leads to utilize when managing tickets, this will reduce the error rate(s) significantly so my reports don't break as much :D

very clearly explained to an HTML nitwit like me on the updated docs.

This issue is CLOSED!

Thanks