And who knows the fix to some of these issues might be a hell of a lot more worked now that the bug has been baked in and the "real" fix is herculean now.
Yes, there are plenty of those tickets in GitLab public tracker, for example the "Allow defining scheduled pipelines triggers as yaml" [1] one is a good example. But still, it's a 6 year old ticket that has been clearly shuffled around with nobody taking full ownership of it, probably because it was never deemed important by higher level product management.
And this is for a "feature" and it's the first that came into my mind for $REASON, but there are similar tickets for very annoying bugs.
That’s been my last couple months. “Yes this is a bug / not optimal, but all the imagined paths / solutions are not great or a mountain of new code / requirements …”