Scrum burndowns should not be related to time spent at all. That’s not an actual agile technique, that’s your company not trusting you and not understanding how software works. Story points that are meant to represent unknowns and complexity, not hours, used for estimation and burndowns are one solution to this

At Gitlab we try to reduce the scope of tickets so that they all ship in the same sprint.

We measure efficiency by measuring the MR rate, the number of merge requests in a month devided by the number of engineers. To game the number you have to split work up in smaller Parts which helps cycle time, coordination, predictability, and quality, for example smaller changes are easier to review.

That isn't agile. Tickets should be based on relative effort, not hours, and certainly not more hours being better.