
My case is also a little different (it's an ancient style glass making companyâthat modernizes it to digital factory, I'm Software QA engineer. I watch the workâof Monitask with my team from our IT office in Thessaloniki, where we made our ERP and production tracking systems. Though perhaps itsâmost valuable feature was its neutral, datadriven proof of work. And when Iâm inâthe midst of a testing sprint â whether manually checking UIs or writing Selenium scripts â itâs nice that project-based time tracking (like âERP v2. 3 Regression Testing"), used to record whoâdid what. This has been critical as we figure out a way to argue with schedule leads about deadlines when they are used to thinking in terms of physical production monthsârather than hours. Well its also saved my ass quite a few times when I had to show the external dev team some super complex bug repro path and didn't want them spending the next 4 hrs typing in that address in, clearing their cache, etc. which did used to be a real burden before we test on local: "Oh your machines cached our old js? let me clear oh wait, what is happening?" It has been a life saver! (the screenshot one - seems like privacy blurredâor something if you intentionally try with sensitive content) Review collected by and hosted on G2.com.
The initial adoption faced skepticism. The concept of "monitoring" knowledge work was anathema within a production culture, andâmet initially with some skepticism. I was required to become a champion for the tool, and actâas the intermediary between IT and factory leadership, in order that QA's otherwise nebulous work could be turned into solid "project hours" they were comfortable billing. Theâtool is in fact formally rigid. It completely fails to realize, e.g., watching logs or testplans for hours (with no frequent mouseclickâevents) as not being "idle". Had to blow out the use of the Manual activity note feature, extra adminâoverhead but small and uniform.. Review collected by and hosted on G2.com.