No need to say Zammad is brilliant. But I lack a bit of functionality.
In usecase parlance: as a user I sometimes have the need to enter driving distance with a ticket article so I can generate a bill each month that accounts for both time and distance driven.
I can extend ticket objects, but not ticket article objects so adding an attribute to a ticket article is not an option.
I finally figured out a possible workaround for this so I can administrate driving distance per ticket article if I happen to spend time outside the office. The time_unit field in ticket_time_accountings is numeric(6,2). I could enter the distance as the part after the decimal separator for distance up to 99 units (Km, miles).
Of course later I have to split the field and sum separately.
My request would be to change the field to a float. I think the performance impact is nil but it allows for distances larger than 99 (meters, Km, miles) to store.
Looking forward to what the Zammad devs think about this one