Does anyone on this forum have the skills and software to set up a bug logging system for us??

Not sure I fully understand what your goal is. But one can allways use Atlassian Jira ( https://www.atlassian.com/software/jira ) or Bugzilla ( https://www.bugzilla.org/ ). 

Thanks . Will take a look !

just wanted to see if one can make some order from this chaos 

Is it really needed to have a bug-system? I guess that there are not THAT many bugs, so it is needed???

I am q quite happy with my 955 Solar, I only have a few remaining issues - Swim Strokes, Cadense, VO2Max calc - Which I guess all are going to be fixed at the next release.

Would be nice to have a clear overview indeed...

Perhaps a simple excel sheet (online) would be something already,,, Just a list of the known issues with possible links to topics here and in which firmware versions they occur (or are fixed)?

One of my reasons to start that main topic back then was to prevent multiple topics of the same issue to be created (but because it was not stickied and disappeared to later pages that certainly didn't always work) and to have a single overview for Garmin (well... no clue if they actually used that).

But it's kinda annoying to maintain and to keep up to date with everything ;)

Part of the issue is that Garmin are not using their own beta program properly. Every single issue is Under Review. This gives us no visibility of whether an issue has been acknowledged or being worked on. This ultimately results in multiple posts of the same issue, across the beta builds. 

The problem is more that there's no visibility of the triage process happening. I appreciate that Garmin, like most companies, doesn't want their internal processes to be visible to all. Some companies are concerned that having a publicly visible list of acknowledged bugs could affect sales and provide their competitors with some sort of marketing advantage.

This doesn't help us, the users, to work out what's happening, leaving us frustrated not knowing if anyone's working on the thing that's annoying us.

Yes, keeping track is very important.

But there are so many bug reports and I find that the team is very slow with fixing them.

Now I don’t know the resources which they have.

A company like Garmin should know that when they release a major update or new devices they should get the most resources so the bugs get fixed quickly.

I Just dont get it. What are you hoping for that you can gain from this acitivity? You want to mail a list of bugs to Garmin once a week? Or is it for your own "fun" to keep track of bugs?

Many of you are probably going to say "I am a developer of profession, and I have never seen something as poorly as Garmins development-eco-system". What the heck! I bet that you do NOT have the same level of complexity as Garmin with more than 40 different watches/versions of watches to keep track of.

If you actually have taken your time to read the press releases from Garmin, then you would know that they have spent the entire spring of changed their development processes, merging teams of development, making fewer releases but with higher quality.

So what you might be doing if you move forward with stuff like this, you are going to slow down fixes even further. Have you even wondered that the people of Garmin that spends time in here on the forums are also the same persons that do the development/fixes that we all want.

So I would say - "Stand down" and wait. 

Things WILL get fixed.

Partly for interest to see what is going on and what the solutions people report and also to help us be able to navigate the forum.

Yes I know about the development cycles but these are not largely new features but marketed and included items that don't function as designed.