You do not need permission, a template, or a category. Start a new problem and describe what happened in your own words.
What to write
Write it as you would describe it to a colleague who was not there. Three things make a report actionable:
- What happened, plainly. “The monthly invoice run failed again” is worth more than “Finance issue”.
- Where and when. Which system, site or team, and roughly when. If it keeps happening, say how often.
- What it affected. Who was held up, what could not be done, what had to be worked around.
Anything you already suspect about the cause belongs in there too. Do not hold a report back because you are not sure. A half-explained problem on the record beats a fully understood one that nobody logged.
What you can leave alone
- The title. One is written for you from your description. Change it if it has missed the point.
- Who it goes to. It is routed to the team that owns that kind of work.
- How serious it is. Every problem is graded on arrival by how far it reaches: organization wide, department level, or individual. That grade is what lets leadership see the serious things without having to read everything.
After you submit
The problem appears in the list with a title, an impact grade and an owner, and from that point the thread on the record is where the work happens. You stay attached to it as the reporter, so you can follow what happens without chasing anybody.
If it is urgent
Kumiko is a record, not an alarm. If something needs a response in the next ten minutes, phone somebody first, then log it. Logging it is how it gets fixed rather than handled again next month.