| Summary | "Due Date" not recognized on CSV import |
| Queue | Nag |
| Queue Version | FRAMEWORK_3 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | Horde Developers (at) |
| Requester | jg (at) cms (dot) ac |
| Created | 12/10/2005 (7156 days ago) |
| Due | |
| Updated | 08/08/2006 (6915 days ago) |
| Assigned | 12/17/2005 (7149 days ago) |
| Resolved | 08/08/2006 (6915 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Taken from Chuck Hagenbuch
The main problem here seems to be that we simply never implemented
importing datetime types - we handle dates, we handle times, but not
datetimes. The code for it as far back as I could trace is simply empty.
One possibility here, and also in the date import, is to use strtotime
to try and guess what format the date is in. I'd also like to add
support for showing the user what value would be imported (using the
sample row) with each format choice.
State ⇒ Assigned
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ "Due Date" not recognized on CSV import
Queue ⇒ Nag
use unixtime on import.
But Nag doesn't recognize this field on import with a unixtime value. E.g.:
"name","desc","category","due","priority","completed","alarm","flags"
"test","test",,"1134251107","3",,,"0"
won't show up with a correct "Due Date" in the overview or details of
that task.