Journyx Timesheet 5.6m3 includes fixes for the following known bugs/issues:

1. Python zipfile module limited by available memory
2. Performance problems when selecting a large number of items for inclusion in reports
3. Adding a project can result in an error message saying "Bad operand type for unary +"
4. It's possible to upload a blank (no selection) receipt image
5. When editing a row on an entry screen, if you click to edit a different row the first row's changes are lost
6. Migration error where some time, expense and mileage records are zeroed out from 4.6 to 5.6
7. Allow disabling of Timesheet cron function with configuration file flag
8. Running the patch tool in some cases can result in a problem when installing DB triggers
9. When using Timesheet Domains a javascript problem is seen on the Projects column
10. Credit card receipt image files rendered as .tif files do not upload properly
11. If you create a new project with Disconnected Client and do not select any groups, the project does not get created
12. User search in reports isn't filtering the list of users in some cases for the permissions of the person logged in
13. When a domain administrator goes to the Logging Preferences screen and clicks on the "View Audit Log" link, a "wtdoc NameError" error appears
14. In certain situations, especially with a very fast server, journal entries and diary note text can get saved in a jumbled order
15. System reports allow some roles to view user extra fields that should be restricted from viewing this information
16. Records with no Timesheet MSPID are being synched back to MS Project
17. When running a report on a user with a "Percent Entry" timesheet, you might get this error message: exceptions.NameError - global name 'recs' is not defined
18. When running a report, debugging information was being added to the debug.log even when the logging was disabled
19. User can't delete their own expense records if a receipt image is attached
20. When users book time for the week, they still show up as having zero hours in the user subtotal
21. Scheduled imports result in error when run using Timesheet Domains
22. Clicking on Save on the My Project list screen doubles record values on entry screens that were previously unsaved
23. Performance problems with reports and "historical" extra fields on Postgresql database servers
24. Email notifications sent by the system aren't working in sub-domains when using Timesheet Domains
25. Migration from 4.6 to 5.x can fail in a partial state on time record attributes table
26. When installing DCOracle2 drivers on AIX Version 5.X with Oracle 8i the jtorainstall fails with an error
27. Installation of the DCOracle2 drivers on AIX fails at the make step with an error
28. The project dependency import does not allow multiple projects per line
29. Memory problems when archiving and purging a large (< 1 mill.) number of records
30. 0 character is being added on to the end of text extra fields with numeric values
31. In some cases the credit card upload will get confused and fail to recover from errors resulting from a file not found
32. Option to designate whether or not a user can copy a report is being ignored
33. Allocation entry screens aren't working with decimal entry format
34. The email notification tag for primary approver is showing the wrong name
35. Some reporting options when selected will fail immediately with an ImportError
36. When applying DB2 drivers to AIX V5.X the driver build will fail with a file not found error
37. The enhanced sheet status report will use the wrong date format in some cases
38. The jxAPI SOAP method getApprovalTemplates() was not returning the template name
39. Some configurations running with the audit/timestamp feature experienced poor performance when updating that table
40. View Time Report button showing all users instead of just selected user for timekeeper
41. Import creation will sometimes fail with a ValueError exception in jtcron.py
42. A database SQL error may occur when running a Report with the "Automatically include Project Descendents in Report" option checked
43. After migrating from Timesheet version 4.6 to version 5.6 or later, Rates & Rules calculations can fail - no rates are generated
44. If an entry screen has only 1 column, saving records may fail with a ValueError: int() literal too large
45. If you set up a day-range period for 0 days, you can't access periods again
46. When you perform an import of any object with visibility settings, such as projects, tasks...you get a NameError if the visibility is changed
47. It is possible to get the following traceback error during project import: exceptions.IndexError list index out of range
48. When approving, the following error may be encountered: 1 error(s) occurred. The Project "" is hidden. Journals associated with this Project cannot be changed.
49. ID of approving user should be reflected in Approval Report sheet notes
50. Daylight Savings email notification spam problems
51. Time records prematurely flagged as committed when using Allocation Entry screens
52. Currency conversion in reports doesn't work without having mileage reporting enabled
53. Allocation Entry screens with corrective records and blank comments cause error upon resubmit for approval
54. Approval of Allocation Entry time may fail if the user no longer has access to the referenced projects
55. When a timekeeper submits a sheet, the arrows for navigating to other periods break
56. Group import shouldn't use display names as unique IDs
57. Backup approver queuing should be able to occur earlier than day after period
58. Deactivated time approvals still show approve button
59. Microsoft Internet Explorer will refuse to display plain text reports in the browser
60. Task (all code) modification screens limiting names to 30 characters