Fracttal ideas (English)

Currently you can only link a new Work Order back to a previous WO. This is good, but it does not meet the need of Field technicians that need to 1) create follow-up Work Requests/ Work Orders directly from a PM WO and 2) have the new WR/WO linked...

At the moment WO priority descriptions are "High High", "High", "Medium" "Low" and "Low Low" Many customers have their own priority descriptions that they want to use. Fracttal already use Priority IDs (1 - 5) as pert of its API calls, rather than...

It takes to much time to close one work order at a time, want to select multiple work orders and close them all at the same time. The same way i can select multiple queues, i want to select multiple work orders.

Usually the typical maintenance tasks are classified as preventive or corrective. I miss a clear report (or dashboard) with it.

(In Kanban View) Group Sub Tasks in Work Queues under a Asset heading, much like the old version, this will make the viewing of different Sub Tasks per Asset easier to see and manage.

cuando se pasa una Ot de proceso a revision se deja pasar sin que se haya firmado la Ot, sugiero que la Ot tenga la condicional que no se pueda cambiar de proceso a revision si no esta firmada o aceptada por el cliente

When analyzing an equipment performance a single metter is never enough for assessing the asset's condition. The iteraction between multiple variables is the best way to diagnose a possible failure. Lets seay you have one water pump. There are 12 ...

that could help to contabilize the effective time used in a task made in different days.