Check database before release

[GHLasse]

A couple of things I would like you to remember to check before releasing the new version:

• [x] synchronize the database content (as usual)
• [x] ensure that the database columns are updated (as usual)
• [x] check for comments in printing data hinting on printers being used for Malyan rather than the indicated printer. Switch those to the printer_id of the Malyan (Printer 32)
• [x] ensure that prints have the correct status. Some prints in the printing history seem to have been left as Approved. Change them to completed and assign the system user as the one who completed the process.
• [ ] ensure that the order of broken periods and prints is correct. Any printer faults (broken/ missing) don't have a time stamp on them. Go through the printer histories and confirm that they are in synch with the printer usage. Basically no printer usage should occur on the same date after the printer broke. If this still happens: Just adjust the time stamp so that the printer is registered as broken a minute after the last print finished that day.
• [x] ensure that printer issues are finished correctly. It seems like some printer faults have a completion date even-though they are still active. Others don't even though they finished and other prints and issues occurred after them. Assign reasonable dates to them please.
• [x] check printer status. Some printers are shown as missing even though we don't have any message registering them as missing. Just put them as available. We will ask demonstrators to check all the printers again and register missing and broken ones if the status is available.
• [x] add a couple of issues from the historic data. If you remind me of the columns, I will give you the details.

Please let me know when you are ready to push, Please don't push before Thursday, so we can give Tim and Katherine time to check the cost codes which have expired. Also, I am happy to help looking at the printing history with you.

[sb2g14]

printer 15: Status available but has unresolved issue printer 26: Unresolved issue shown as resolved in the history printer 31: The printer status is missing, issue opened but there are successful prints after

[GHLasse]

printer 15: Is it enough to just change the status to "broken"? if there are no more prints done on it since, then assume it is broken, and let people resolve the issue if they think it's fine. printer 26: if there is no date closing the issue in the database, then it's an error in php - would need to look at the code with you. printer 31: yeah, that's a bit messed up. I wonder how an Up BOX went missing... I think those prints are for printer 32. The printer is missing, so no one can print anymore now (not even demonstrators).

I have a suggestion how to deal with scenarios like with Printer 31: changing the status on the printer from broken to missing doesn't add a comment but creates a new issue. In that case we have two open issues for a printer: the printer is broken AND it is missing. They can then be resolved individually. We do need to make sure that resolving an issue checks for other open issues to update the status. -> I think I will create a new issue for this and we can discuss the details there.

[GHLasse]

I think we did the best we could on this one :-) Will ignore the order (at least for now)