Learning path

Module 5: Managing Assets and Inventory within Tickets

Updated

Goal: run repairs through tickets so every part used and every device touched is recorded automatically, with stock levels kept up to date without extra data entry.
Time: about 20 minutes, using one test ticket.

Before You Start

  • Finish Modules 2 and 3, so you have assets and inventory to work with.
  • You need the Edit Tickets permission. To close tickets, you also need Close Tickets.
  • Tickets are in the left-hand menu under Tickets. For the full page reference, see Quick Guide: Tickets and Quick Guide: Ticket Details Page.

How Tickets, Assets and Inventory Connect

  • Devices: a ticket can link miners, assets and infrastructure. Each device's tickets show on its row in the Assets table and on the miner's details page.
  • Inventory: parts added to a ticket are deducted from stock as soon as the ticket is saved. Removing a part from the ticket returns it to stock. The Assigned column on the Inventory page shows how many of each item are on tickets.
  • Low stock: if using a part drops the quantity below its Notification Amount, the low-inventory email goes out.
  • History: each ticket has its own history, and each asset's history records when it was added to or removed from a ticket.

Step 1: Create a Ticket With Devices

  1. Go to Tickets and click the add button in the corner of the table.
  2. Enter a Name and set Priority and Status. These three are required. Pick a Ticket Template if you have one.
  3. In Devices, search for and select the miner or asset being repaired.
  4. To change the miner's state at the same time, turn on Update Miner State and choose, for example, In Repair.
  5. Click Save.

Shortcuts: select assets on the Assets page and use Bulk Edit > Open Ticket, or create a ticket from the Pull Miner form when you pull a miner off the rack.

Step 2: Add the Parts You Used

  1. Open the ticket's details page.
  2. In Inventory, add the item and set the quantity used.
  3. Click Save.
  4. Go to Operations > Inventory and check that the item's quantity went down and its Assigned count went up.

Note: Create Individual Tickets, which splits a ticket with several devices into one ticket per device, isn't available once inventory is attached. If you plan to split a ticket, do that before you add parts.

Step 3: Finish the Repair

  1. Add a comment describing what was done.
  2. If the miner is going back into service, set its state back to Deployed from the ticket. See How To: Change The Miner State In A Ticket.
  3. Change the status to Closed. See How To: Change The Status Of A Ticket.

Step 4: Check the Record

  • One ticket: open the ticket's menu (…) and choose History to see every change, who made it and when.
  • All tickets: use View History on the Tickets page. You can filter and export it.
  • The asset: on the Assets page, open the asset's history to see when it was added to the ticket.
  • Paper copy: choose Print from the ticket's menu to open a PDF for the repair bench or an audit file. See How To: Export And Print Tickets.

Done When

  • ☐ You've created a test ticket with a linked asset.
  • ☐ You've added a part to it and seen the inventory quantity drop.
  • ☐ You've removed the part and seen the quantity come back.
  • ☐ You've checked the ticket's history and the asset's history.
  • ☐ You've printed the ticket.

Next

Continue with Module 6: Reporting and Exports.

Last verified: November 19, 2026

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Can't find what you're looking for?

Our support team can help with setup, hardware and billing questions.

Contact Support