Let’s put a story point estimation on that. Then we can extrapolate time range and risk.

How’s it going so far?

The solution to this problem. . .

is that they have to create a support ticket with you, that you then put in progress, and you walk them through your documentation, and then log your time spent onto that ticket. (/s)

There’s an alternative to creating too many tickets that only add overhead and then make it harder to get into the project. Creating a good amount of tickets.

I took the OP reference as demand for ticket creation when they don’t make sense and only hinder development through unnecessary overhead. E.g. creating a ticket before a quick analysis, or creating individual tickets when one story/feature ticket would be enough. Or more specifically in this case, having to create one before fixing a critical blocker.

EoD? End of December? End of Death? (reference to world going to end)

man oregano => https://man.cx/oregano

oregano - GNOME application for schematic capture of electrical circuits

I doubt it is about that though…?

https://github.com/doitsujin/dxvk/releases/tag/v2.5.3