Bugs aren’t restricted to a single app. If it’s a bug, then it’s a bug for everyone. It’s just that it may be more noticable to some people and not to others. You may be noticing it more than others because you have a lot more entries packed into a very tight time slot. These are the scenarios that Glide needs to see. I could have a calendar with a single entry where everything looks fine on the screen. If I create a ticket, then they are going to say… what’s wrong, it looks fine. They need to see how it looks in your app with your specific use case.
You can do nothing and hope that maybe something changes with the calendar someday, or you can create a ticket to make Glide devs aware of your specific problem and maybe have a slightly better chance of something being done to fix it.
Speaking from experience as a software engineer, it is next to impossible to fix a bug if I don’t know how to reproduce it, or that it exists in the first place. Create a ticket if you want something to be done. Examples and thorough documentation are priceless to devs when trying to fix bugs.