How to make sure that bugs reported to the support team are not forgotten?

Hello XForms enthusiasts,

There are many issues with Xamarin.Forms, some of them major and blocking an App from being released or needing a dirty workaround to make it bearable. When our team runs into such an issue we normally perform the following steps:

1. isolating the bug in a minimal code example
2. pushing the example into a public GitHub repo
3. sending our findings to support@xamarin.com

What normally happens is that after two to six mails back and forth with the support team, they just file a new bug in the Bugzilla system and leave it be. There is no estimate for when the issue will be fixed, no suggested workarounds and we've never seen such a bug filed with higher importance than "normal". How do you make sure that the bug won't get lost in the pile of issues? And if the issue is pressing (and very often it is) how do you get a hot fix? We execute the following extra steps to seek for possible workarounds:

1. writing a StackOverflow question describing the problem and asking for a workaround
2. posting in this forum
3. investing time and money to find a workaround on our own

That worked for some cases. Most popular example is the performance problem when using Labels. We wrote to the support team on 14. October that our App is to slow for a public release due to the inefficient layout recalculations caused by the Label implementation. They simply entered the bug as "enhancement" (https://bugzilla.xamarin.com/show_bug.cgi?id=23822) and put it our of their mind!!! After two weeks of waiting and our deadline approaching we pressed the support team again. They told us to wait while they will talk to the XForms team. We're still waiting for a response or update. So we wrote to this forum and started digging into the issue our self. This mix finally beard fruits and we developed our own "FixedLabel" which directly derives from View and is a reimplementation of Label without the costly relayouting.

Has anyone experienced similar "adventures" with the support team? How do you keep track of the bugs and hacks in your Forms applications? Are you trying to remove all the workarounds in your code when a new release is published? What if the issue is still present? I feel that the currently practiced approach is to write a comment into the release announcement thread and hoping that @JasonASmith will promise to fix it soon. Or has anyone found a better workflow?

Regards,

Rodja