~20 min Beginner

Handle a broken item end-to-end ​

Something broke. This tutorial takes you through the whole chain: report the problem as an issue, take the item out of service automatically, schedule the repair, log the performed work as an event, and close the issue — which puts the item back in service.

The point of doing it this way instead of a quick fix on the side: every step stays linked (issue → repair reservation → repair event), and the item's condition history tells the story afterwards.

Step 1 — Report the issue ​

  1. Open the item's page, click Perform task and select New issue. The item is added automatically (you can also start from the Issues page with the New issue button).
  2. Write a short Issue headline — this is what shows in the issue listings.
  3. Set the Resolve before deadline. If the issue is still open or in progress at the deadline, the participants are notified.
  4. Pick the Primary person responsible, and optionally a Location and more Participants — all participants are notified about the issue.
  5. Check Mark item(s) as Inoperative while issue is open. The item's condition then automatically changes to Inoperative now, and back to Operative when the issue is closed — the item is taken out of service for as long as the issue lives.
  6. Click Create issue. The new issue opens on its own page.

Step 2 — Document the damage with pictures ​

Pictures often say more than words. On the issue page:

  1. Click Add files on the Attachments card and select photos of the damage — or simply drag and drop files anywhere onto the issue page.
  2. For details that belong to a specific point in the text, edit the description and use the image button in the toolbar (or paste an image directly) to place it inline.

Images show as thumbnails in a gallery; other files (service reports, repair quotes) are listed with name and size.

The Attachments card on an issue page.

Step 3 — Start work on it ​

When someone begins looking at the problem, click the colored status badge in the top right of the issue page and pick In progress, so everyone can see resolution has started.

Step 4 — Schedule the repair ​

If the fix needs to be planned rather than done on the spot:

  1. Click the ⋮ menu in the top right of the issue page and choose Schedule repair….
  2. The new-reservation window opens prefilled with the issue's items, a name based on the headline ("Repair: …"), the Repair classification, and a link back to the issue.
  3. Adjust the period and details, then save.
Schedule repair… in the issue's action menu.

The issue's info card now lists its Scheduled reservations with start time and status, and the reservation shows which issue it came from. (Scheduling requires permission to create reservations — not issue permissions.)

Step 5 — Do the repair and log it as an event ​

When the repair has been carried out:

  1. Open the repair reservation and click the More menu. Because it's classified Repair, Create event is listed first, marked Default.
  2. The event opens with the reservation's information copied in and inherits the Repair classification. Describe what was done (parts, cost, who did it), then save.

The reservation is marked completed, and the repair now lives in your events history — the item's service log under its Activity tab → Events.

Step 6 — Close the issue and verify the condition ​

  1. Back on the issue, click the status badge and pick Closed.
  2. Because the issue was created with the auto-condition option, closing it returns the item to Operative — it's back in service, no separate condition change needed.
  3. To verify, check the item page's condition status, or the condition history: Logs → Condition changes in the main menu, or the item's Activity tab → Conditions. You'll see the drop to Inoperative when the issue opened and the return to Operative when it closed.

What you accomplished ​

  • An issue ticket with a deadline, a responsible person and photo documentation
  • The item automatically out of service (Inoperative) for the whole life of the issue
  • A repair reservation created straight from the issue, linked both ways
  • The performed repair logged as a Repair event — part of the item's permanent service history
  • The item back to Operative automatically on close, with the full story in the condition changelog

Where to go next ​

Related articles