pegro

Changing that method would be possible, but I don't like it. I don't want to allow a malicious API client being able to change importent properties like `Record.Cutin` without creating...

Mh, not sure that introducing all that API, tables and model code only to avoid that if clause is worth it?! What would be the conceptual difference between those two...

I assume those "average" numbers won't change much during an encoding. Using the latest update on an encoding fps property should already give you a good overview how an encoder...

You mean `setVolatileTicketProperties`? We have properties for tickets and projects. But we would never merge them with the existing properties, right? So that changing the effective `Record.Cutin` propety still gets...

Like I said, I don't want to allow anybody changing important properties without logging. I know the tracker doesn't know or care what is important, but I just feel bad...

What about storing some actual (and sanely parsed/handled) HTML/XML? Like a property value of `Link name1Link name2...` I know it's still a hack, multivalue properties would solve that, but this...

I'd only start thinking about adding the level of complexity required for multi-value properties, if we have enough use-cases. Having multiple persons or links attached to a ticket, which both...

We are not using ltree features as far as I can tell. In the API handler I only use the model and I didn't find any operators specific to ltree...

Properties on encoding profiles get propagated to all projects assigning them. So you can't have automatic-checking disabled in a project, while having it enabled in another!? I would propose introducing...

Are both of these properties relevant to the tracker itself? Different behavior? Showing/hiding buttons? I like to think about the tracker without having too much details of how crs-scripts (or...