The number of cores (CPU type) is actually limited to 8 cores, but we get now CPUs with 16 cores donated (and may-be more in the future). Not urgent, but we should allow tagging higher number of cores than 8, thank you. Ralf, Labdoo.org (Germany)
Javier recently made a question that made us realize our "Delivered" counter underestimates the actual values of delivered laptops. This is because a laptop delivered (S4) that later on is recycled (S6) stops counting as delivered. The metric should look at all the historical states taken by a laptop to truly capture the right number of laptops delivered.
(I posted on LGS Team Wall but maybe I should have posted on Team Software Development?) After I updated the status of 2 dootronics, these messages below (and attached image) appeared. - Unable to send e-mail. Contact the site administrator if the problem persists. - There was a problem sending an automatic message, please contact Labdoo at firstname.lastname@example.org (link sends e-mail)...
This bug was found by Javier. In the dootronics dashboard, for some laptops their serial number shows as NaN, even though the number is set.
A user (Elena) found that there was no description for the fields in the Labdoo dashboards. While some are intuitive, for other fields it might be difficult to know their meaning. This task is about adding helper descriptions for all fields.
What versions of Ubuntu does the Labdoo software platform work with? Is it only Ubuntu 1.4.04?
Currently the list of dootronics selected on a user's dashboard is picked from this query: $queryUser = "(SELECT tUser.entity_id FROM (SELECT entity_id FROM field_data_field_tagger WHERE (field_tagger_target_id=:uid) UNION SELECT entity_id FROM field_data_field_manager WHERE (field_manager_target_id=:uid)...
This should be done by providing start and ending IP values. This is similar to this other feature but in this case we want to print large ranges of consecutive IDs without providing each ID one by one: https://www.labdoo.org/content/printing-multiple-tags-avoid-paper-waste-0
This task is about looking into the Labdoo cron job and seeing if we can optimize both its execution time and the time it takes to load a first page after the cron job has run.
Hello all, Some of you noticed that recently geolocation maps were no longer showing up for dootrip objects. This issue has now been fixed and so you should now be able to geolocate dootrips again. Sorry for any inconvenience and thanks for your patience! https://www.labdoo.org/content/dootrips-dashboard