API Write Access for Ticket Custom Fields
Foreman's ticketing system does a great job tying repairs to serial numbers and exporting ticket data with custom fields via CSV. It would be a huge unlock if we could also update those custom fields through the API.
Our use case: when repair invoices come back from vendors, the serial numbers and costs are already structured in a spreadsheet. Being able to match those to open tickets and write the repair cost into a custom field programmatically would let the entire repair to billing cycle flow through Foreman without manual data entry.
Here's what the full pipeline looks like:
Miner Pulled → Ticket Created (serial number linked) → Sent to Vendor → Invoice Received (serial + cost) → [API writes cost to ticket custom field] → Monthly CSV Export (costs included) → Client Billing
Everything before and after the bracket already works in Foreman today. This one endpoint would connect them.
Comments
1 comment
Making the templates section more dynamic would be very helpful as well. Currently if any options from a dropdown type custom field for a ticket is deleted, errors arise. Existing tickets should have their own memory so they don't break when we update templates and custom field values in the future.
Also, tickets for site clients are viewable for each site client, but all tickets should be viewable from the master account.
Please sign in to leave a comment.