Tickets
Eight illustrative cases show assigned, waiting, reopened, resolved, and closed work. Track the owner, next action, due date, asset tag, and resolution notes. Formulas show ticket age, recorded work minutes, and due health.
Keep the issue, owner, next action, due date, and handling effort together. Start with the Jodoo app for connected work, or download the editable Excel workbook for a small shared register.
Explore with sample data. Adapt fields, views, and workflows for your team.
Three sheets, sample cases, dropdowns, and formulas. Prepared for 100 tickets and 100 work entries.
Eight illustrative cases show assigned, waiting, reopened, resolved, and closed work. Track the owner, next action, due date, asset tag, and resolution notes. Formulas show ticket age, recorded work minutes, and due health.
Record multiple activities against a ticket ID. Each row holds its work date, technician, activity type, minutes, description, and correction note. Per-ticket totals are calculated from these entries.
Edit category, priority, status, and work-type options. Use consistent spellings while existing tickets remain in use, and extend the validation range if the list grows beyond its prepared rows.
“Waiting” is not enough. Record what is needed, who will obtain it, and the date for following up. The workbook flags an open ticket without an action date separately from an overdue one.
Update the existing ticket and log further work against its ID. Create another ticket only when it is a distinct issue, not merely another conversation about the same fault.
Record the resolution and confirm whether the requester can work again. Reopen the case if the fault returns, retaining useful notes instead of overwriting them.
The file is useful when a small group can agree who edits it and when. Its prepared capacity is 100 ticket rows and 100 work-log rows; extend formulas and validation beyond those ranges.
Use linked records, assigned review tasks, assignment rules, and operational views when several people maintain the same process. Configure permissions and notifications in Jodoo rather than expecting an Excel formula to enforce them.
An XLSX workbook with Tickets, Work logs, and Lists sheets; eight sample tickets; work-log examples; dropdown options; per-ticket work totals; and next-action due indicators. No macros are required.
Set the As-of date on the Tickets sheet. The sample uses a fixed date so its examples are reproducible. The due indicator compares the next-action date with that date; it is not a business-hours SLA calculation.
The prepared ranges cover 100 tickets and 100 work entries. Beyond those ranges, extend the table, formulas, totals, and dropdown sources, then test an added ticket and work entry.
That depends on how you store and share it. The file itself does not establish user permissions, reliable task assignment, or change-approval controls. Use the app when those are required.
Clean the IDs and option values before importing. Importing rows does not automatically create the app’s linked work records, routing rules, or approval workflow; configure and verify those relationships as part of the move.
Inspect the populated Jodoo app, or use the workbook as a clear starting point before adding team workflows.