Summary | Smartphone view: Estimated time field handled incorrectly |
Queue | Nag |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | thomas.jarosch (at) intra2net (dot) com |
Created | 10/17/2012 (4644 days ago) |
Due | |
Updated | 10/27/2012 (4634 days ago) |
Assigned | 10/18/2012 (4643 days ago) |
Resolved | 10/18/2012 (4643 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
commit 8f2e561b3db94b55af7f7ad95e11cd39484c9861
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Thu Oct 18 10:36:42 2012 -0400
Bug: 11543Fix generation of estimate data in Nag_Task::toJson method.Wish all bugs were this easy to fix...
nag/lib/Task.php | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/8f2e561b3db94b55af7f7ad95e11cd39484c9861
commit 45e661ca0a87c013ed5c66b8fcc20cf6a9d8add5
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Wed Oct 17 10:35:44 2012 -0400
Bug 11543This is not a date/time field.nag/lib/Task.php | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
http://git.horde.org/horde-git/-/commit/45e661ca0a87c013ed5c66b8fcc20cf6a9d8add5
commit 8f2e561b3db94b55af7f7ad95e11cd39484c9861
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Thu Oct 18 10:36:42 2012 -0400
Bug: 11543Fix generation of estimate data in Nag_Task::toJson method.Wish all bugs were this easy to fix...
nag/lib/Task.php | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/8f2e561b3db94b55af7f7ad95e11cd39484c9861
State ⇒ Assigned
I've set an "estimated time" of 160 in the normal app.
The estimated time field shows up empty in the smartphone app.
State ⇒ Resolved
commit 45e661ca0a87c013ed5c66b8fcc20cf6a9d8add5
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Wed Oct 17 10:35:44 2012 -0400
Bug 11543This is not a date/time field.nag/lib/Task.php | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
http://git.horde.org/horde-git/-/commit/45e661ca0a87c013ed5c66b8fcc20cf6a9d8add5
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Smartphone view: Estimated time field handled incorrectly
Queue ⇒ Nag
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
when you are in the traditional view of nag, you can enter an
"estimated time" for a task as floating point number.
In the mobile view of nag, this fields seems to be interpreted as date field.
The value is often "1970-01-01T01:02:40" and you'll also get a "Failed
to parse time string (1,970.00)" error popup when you enter an
absolute value.
Cheers
Thomas