#1399 Changes of date to an effort record are not kept
I don't think this be a new issue, I'm just now reporting it.
I wanted to record a week of vacation, with one record for each day not worked. So I copied a past vacation day's record, and edit the new record to change the date. I make the date change to the start date field, tab to the end date field, which results in the warning that "start must be earlier than stop". I change the end date field, which removes the warning. I tab out, and click <Close>.
The change to the start date of the record is not kept. Even though while I was editing the record, it appeared to be successfully set, upon exit, it is lost.
A similar problem also occurs in other contexts for start time when copying a record of an effort for a later time period, when the new start time is later than the old end time.
A fix was made and checked into the source code repository of Task Coach. The fix will be part of the next release. You will get another notification when that release is available with the request to install the new release and confirm that your issue has indeed been fixed.
If you like, you can download a recent build from http://www.fraca7.net/TaskCoach-packages/latest_bugfixes.py to test the fix.
Because a fix has been made for this bug report, the priority of this report has been lowered to 1 and its resolution has been set to 'Fixed'.
Thanks, Task Coach development team
This bug should be fixed in the latest release of Task Coach. Can you please install the latest release of Task Coach and confirm that this bug has indeed been fixed?
Thanks, Task Coach development team
Hi! Happy to be announcing, all these years later, that Task Coach is now updated to Python3 and development is finally active again, thanks to new volunteers. The project has now moved to https://github.com/taskcoach/taskcoach
I'm using it myself, and things are working better than ever. Packages are available for some common Linux systems and for Windows (note that it isn't recognized by Windows Smartscreen but can be installed by accepting the warning anyway)
We'd love to have you test the updated program, and post any issues that arise there at GitHub. We won't be continuing with SourceForge, just clearing out old issues and letting people know about the move.
Also notice that the in-program "check for updates" just goes to the GitHub link, it no longer will automatically alert you about updates. To get alerts at this time, you'll need to "watch" the releases at GitHub.
Cheers