Hi there,



Now this is a story all about how...

We had a product outage last week Friday evening, after moderation hours. SoundCloud users could not upload their tracks properly.



Some of our users would then come to the community and post about it. Luckily, many of them found the topic that was most recently created and contributed w/ replies. This helped them understand that this was a system wide issue rather then an isolated edge cases. Best case scenario.



However

There’s always people who miss this one collective topic for one reason or another. They go on and create a new topic. A duplicate if you will.



Monday morning

I start moderating. After moving the replies & original post of these duplicate to the one collective topic, I noticed that the number of replies will increase (obviously), however the views of the previous duplicate don’t get added. They go to Nirvana. Also, there is not an easy way for me to figure out how many unique contributors this topic has (or is there and I just didn’t notice?)



Back to the issue, and our internal follow up

When filling out our internal report and providing the community impact, we’re not just using the amount of replies, but the amount of views, which is drawing a much more accurate picture for our use case. Knowing how many individual contributors wrote in about this would also be beneficial.



Views getting not being moved but instead just getting lost has a serious impact on filling out these reports accurately.



Are you still reading? Great! Mission accomplished (hope it wasn’t too boring, and somehow makes sense…)



Any advice, insights, opinions, etc. etc. welcome :)



Cheers

Mathis