{ height: 1%; } - Ruby on Rails and User Interface Design

Important Notice: Reporting Bug

Posted by Richard White Mon, 14 May 2007 22:24:00 GMT

What happened?

• Time entries created using the timer client would be marked as “in progress” (including not setting and end time) until the entry was completed.
• Reports were tuned to not count “in progress” entries since I didn’t want people invoicing based on partial entries.
• Due to things like browsers crashing and computers going into standby entries were being left as “in progress” and thus weren’t showing up in reports.

What’s been done to address this?

• Reporting now includes these “in progress” entries by default, but you can toggle this to compare to previously run reports.

• You can see a list of your affected “in progress” entries here to help you decide if you need to re-run past reports (eg: for invoicing purposes) otherwise no action is required of you.

What else will be done?

• After giving sufficient time for everyone to review their entries, I’ll set all “in progress” entries as completed and remove the “in progress” toggle from reporting.
• The client timer and the API are being changed so that no new entries can get stuck in this permanent ‘in-progress’ limbo. Though it’s a moot point since reporting now includes ‘in-progress’ entries.

Bottom Line: No data has been lost, but some was not showing up in reporting. Check your list of affected entries and decide whether you need to re-run past reports for invoicing purposes otherwise you’re fine.

I thank you for your understanding and apologize for any inconvenience this may cause. If you have any concerns about your data feel free to email me directly.