phpreport
phpreport copied to clipboard
Cloning a task doesn't clone the "telework" status.
[Trac import] Reported by: agomez Original date: Tuesday, 06 April 2010 17:03
When choosing to clone a task in a certain day, the "telework" option is not cloned.
[Trac import] Comment by: jlopez Original date: Tuesday, 06 April 2010 19:47
This bug seems to happen when the telework value cloned was not loaded initially, because javascript code changed its type on the TaskRecord from string to bool when clicking on the checkbox, and the checkbox is configured to read literal strings ('true' and 'false') and not booleans.
[Trac import] Comment by: jlopez Original date: Tuesday, 06 April 2010 20:05
OK, I have changed the javascript code, making a conversion from bool to string, and it hasn't failed again in my version.
Now just wait for the patch to be applied. ;-)
[Trac import] Comment by: jaragunde Original date: Thursday, 15 April 2010 13:32
Patch applied.
[Trac import] Comment by: agomez Original date: Friday, 15 October 2010 15:16
This is not always working.
STEPS TO REPRODUCE THE PROBLEM:
- Go to an empty day.
- Create a new task, mark it as telework and save.
- Push clone button
EXPECTED OUTCOME:
The task is cloned completely but the start time and end time.
ACTUAL OUTCOME:
The telework checkbox of the cloned task is unchecked.
[Trac import] Comment by: jaragunde Original date: Friday, 15 October 2010 16:10
I've checked it's perfectly reproducible. It happens in multiple browsers (I've checked Firefox and Chrome), and only with the steps explicitly mentioned: it has to be an '''empty''' day and the task has to be saved '''before''' cloning.
Autosave may get in your way to reproduce this bug, but it's still valid:
- Create a new task. Leave start and end time empty for now to prevent auto-saving.
- Check "telework" box and maybe fill some other fields.
- Finally, fill time fields and save.
- Clone the task you just saved, the telework box of the cloned task will be empty.
It's not necessary to open an empty day, just make sure that the save operation is only triggered once.
We are in the process of rewriting the frontend for tasks. Any outstanding bugs and enhancements for the old interface will be taken into account as we implement the new design.