GTG

Start/due date is set incorrectly

Bug #1079817 reported by Francesco Turco
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GTG
Fix Released
Medium
Izidor Matušov

Bug Description

I'm running Getting Things GNOME 0.3 on a Gentoo Linux system.

Let's suppose I want to add a task with a certain start date (for example today) and a certain due date (for example tomorrow). I noted there's a problem in the following two cases:

1) If I set the start date first (with the mouse or the keyboard, doesn't matter) and then I set the due date (with the keyboard, it's important), the start date is not correctly saved.
2) If I set the due date first (with the mouse or the keyboard, doesn't matter) and then I set the start date (with the keyboard, it's important), the due date is not correctly saved.

Changed in gtg:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 0.4
Revision history for this message
Izidor Matušov (izidor) wrote :

Bertrand, Francesco> Could you give me example dates you use for reproducing this bug? I am not able to reproduce it :(

Changed in gtg:
status: Triaged → Incomplete
milestone: 0.4 → none
Revision history for this message
Francesco Turco (fturco) wrote :

For example you can set start date to 2013-01-01 and due date to 2013-01-02, in this order, both using the keyboard. It will result in a task with a start date incorrectly set in 2012-12-02.

Or you can set due date to 2013-01-02 and start date to 2013-01-01, in this order, both using the keyboard. It will result in a task with a due date incorrectly set in 2013-02-01.

Revision history for this message
Bertrand Rousseau (bertrand-rousseau) wrote : Re: [Bug 1079817] Re: Start/due date is set incorrectly

I get the very same results on my computer when following these steps.

On ven 23 nov 2012 12:33:24 CET, Francesco Turco wrote:
> For example you can set start date to 2013-01-01 and due date to
> 2013-01-02, in this order, both using the keyboard. It will result in a
> task with a start date incorrectly set in 2012-12-02.
>
> Or you can set due date to 2013-01-02 and start date to 2013-01-01, in
> this order, both using the keyboard. It will result in a task with a due
> date incorrectly set in 2013-02-01.
>

--
Bertrand Rousseau
<email address hidden>

Revision history for this message
Izidor Matušov (izidor) wrote :

Thank you, I can reproduce it now. It is pretty strange :/

Changed in gtg:
status: Incomplete → Confirmed
milestone: none → 0.3.1
Izidor Matušov (izidor)
Changed in gtg:
assignee: nobody → Izidor Matušov (izidor)
status: Confirmed → In Progress
Revision history for this message
Izidor Matušov (izidor) wrote :

Fixed in rev. 1281

Changed in gtg:
status: In Progress → Fix Committed
Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

FWIW I used the diff of that commit to patch my 0.3 install by hand. Would have liked to see a minor bugfix release to include that kind of thing. If you think this could be useful, I could provide the patched file.

Revision history for this message
Parin Porecha (parinporecha) wrote :

Hi Jean,

We are going to release 0.3.1 in the next week.
It has the patched file, plus many more fixes and a fixed hamster plugin.

Thanks

Nimit Shah (nimit-svnit)
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.