Observation created about 5 years agoWhile going through some of the errors coming form Honeybadger, I encountered an error on which Josh had provided some great level of details and context a while ago. He pointed out why the issue happened, left some notes after he attempted to reproduce the error locally, and linked the error to other ones that could be related. Not only that, but he also followed up with a great Clubhouse story! I think this is an exemplary error triaging! Thanks Josh!
Link to the error page: https://app.honeybadger.io/projects/37537/faults/37024875
Link to the clubhouse story: https://app.clubhouse.io/lessonly/story/25020
Observation created over 5 years agoAs we've shared in previous Product All Hands and Team Shares, Ross and Josh implemented a new permission to replace our old role hierarchy. The new permission gives customers the flexibility to control which roles a role can edit and assign to people. Throughout the process Ross and Josh thoughtfully implemented the necessary changes behind the scenes. After all the pieces were in place, they removed this new permission from behind the Platform squad's feature flag this week and made it available to customers rather than holding it back until releasing Custom Roles.
Yesterday T-Mobile reported an issue because they noticed their Creators where unable to Edit Managers even though they had automatic management rights for all people and groups. What they reported was in line with how our old role hierarchy worked, but with the new permission they would be able to give Creators rights to edit Manager roles.
When they reported the issue, Stephen was already scheduling a deployment of the latest updates to T-Mobile's private instance. Allowing us to resolve their issue quickly and empowering them to configure the Creator role to meet their needs.
It is awesome to see new changes having such a positive impact, so quickly after being released! Way to go team!