Where an issue came from and who was involved

An issue raised by another record keeps a link to that record and a snapshot of what was captured around it. Whoever deals with the issue can read the failed question, the photos and the people involved on the issue itself. They don't have to go and find the form.

The Origin tab

The Origin tab appears when a record raised the issue:

• a form submission with a failed item,
• a vehicle or equipment check,
• a chat message promoted with Raise as issue,
• a help-desk request turned into an issue with Raise issue,
• an AI review finding.

When it is there, the issue opens on it. Issues reported by hand through Report issue have no Origin tab. Raised from in Details says which kind of source it was, for example Form submission, Vehicle check, Chat message, Request, AI review or Manual report.

Raised by a form

• The source card shows the form's title, "Submission #{id}", who submitted it and when, and the result (Passed or Failed, with the score as "{score} of {max}" on an inspection). Open submission opens it, if you are allowed to read it. If it has since been deleted the card says "The submission is no longer available."
• Failed item: the question that failed, under its section heading, with the answer given.
• Follow-up answers: the answers that hang off that question, such as its photos and notes. Photos open full size, together, so you can move from one to the next.
• People involved: anyone named in the form's People fields, with the field they were named under.
• Crew on the job that day: the people the schedule had on the job when the form was filed.
• Teams involved: the teams of those people.

For an issue drafted by AI review, AI finding shows what the reviewer saw, with Declared on the form beside it.

Raised by a check, a message or a request

• A vehicle or equipment check shows the check, who did it and when, the reading and notes, and its outcome.
• A chat message shows "Message from {name}", when it was sent, and the text. Open conversation takes you to the chat.
• A help-desk request shows "REQ-{id} · {title}", with its category, who raised it and when. Open request takes you to it. See Requests.

Unless the issue is General, each kind also offers Open vehicle, Open job, Open site or Open equipment for the issue's own record.

Other issues from the same source

When one submission or check raised several issues, Also raised from this submission (or Also raised from this source) lists the others with their status. Click one to move to it.

The snapshot doesn't change

The context is copied when the issue is raised and is never worked out again. If the form is later edited, a schedule changes or someone moves team, the Origin tab still shows what was true at the time. If the source recorded nothing more, it says "The source did not record any further detail."

Recording who was involved

Every issue has a Team: the people and crews involved. It isn't the assignee, who is the one person responsible for the fix.

• When reporting: the Team field reads "Pick anyone on the workspace, or type a crew name and press enter. Leave empty to record your own team." See Raising an issue.
• When triaging: Triage issue › Ownership › Team edits the same list. Add a person, type a crew name and press Enter (or pick Add "{name}"), or take someone off with the cross on their chip.
• One list can mix people and crews, up to 20 names. A crew name can be up to 80 characters and doesn't need to exist anywhere else in Maliru.
• If the people list can't load, the field says so and still accepts a typed crew name.

The names show as Team in Details, as a badge at the top of the record, and in the register's Team column. The register's Filters › Team finds issues by any team on your people's records or any crew typed on an issue, and No team finds the ones with nobody recorded. See The issue register and AI-flagged issues.

Tip: name the crew that was on site even when you don't know who will fix it. The Team filter then shows you which crews keep meeting the same problem.