Why not? That is pretty much how open source and collaborative stuff works in this area tbf. We go through a lot of issues on a daily basis. If they are not in the tracker they will/do get lost. I appreciate you may have raised issues before and some/all may still open, but importantly, they are not lost. So if, when we (or a contributor) gets to work, there is a reference/bug report to work on.
My experience is that raising an issue on github is no more likely to result in a fix than not doing so, especially if it is a cosmetic issue with dashboard 2, which already has a plentiful supply of more important issues to work on.
Generally I don't even raise these small issues here any more. I only opened this thread today because it was possibly caused by the version change today.
Thanks for opening the issue @smcgann99 - I have opened a Pull Request, which actually fixes this and hopefully stabilises the general layouts of Dashboard moving forward. I've done extensive testing this evening, but want a second pair of eyes before I get it merged and released, so it'll likely be published into a new Dashboard release tomorrow.
@jbudd just to echo the above, please do report issues as you find them. Yes, we have a huge backlog, but we are trying to work through it as best we can given our resource-constraints. Also, by putting them onto GitHub, any community contributors can see the smaller/"easier" ones and pick them up.