Less than a day old
Tickets that reach the right team
Any employee can report an issue, such as a printer that has stopped working, and send it to the department that should handle it. Tickets sit between day-to-day requests and project work: a ticket can be linked to project tasks, used to create a task, or used to start a project, depending on the issue. Example: Marketing reports a broken printer, files it to IT, and IT turns it into a project task.
Sample data. A view of the tickets page in Mitarbo.
What you can do
Sent to the right department
Submit an issue to an existing department at a location, with an optional named assignee. Every ticket gets a permanent TKT number that is unique across the company, so it can be found by that number later.
A shared conversation and private notes
The reporter and the handling team follow one shared conversation and its files. Internal notes and files are visible only to the eligible handling team. Shared replies notify the reporter and the current handling team, but not the author. Internal notes notify only the handling team.
Linked to project work
Link a ticket to project tasks, create a task from it, or start a project from it. A link never copies the private conversation and never gives anyone access to the project. Finishing the linked work does not close the ticket.
How it works
Report the issue
Describe the problem, for example a printer in Marketing that is not working. Choose the department and location that should handle it, and name an assignee if you know who it should go to.
Work it through with the handling team
The current handling team can assign the ticket, or put it in Waiting with a required reason. Replies in the shared conversation reach the reporter, and internal notes stay with the team.
Close it, or reopen it
When the issue is resolved, the handling team closes the ticket with an outcome and a shared reply. They close it themselves, even when the linked work is done, and can reopen it if the issue returns.
