Internal and external changelog
Sarah Hum
Right now, the changelog is either fully internal or fully external. It would be nice to be able to have both.
P
Pink Armadillo
Yes. We make changes that we want our employees, especially our Sales, Support, and Customer Success teams to know about – but we don't want to publicize those to our users. (For example, we might have corrected an issue and we don't want to alert users who hadn't noticed it that there might have been a problem.)
Besides employees and current customers, there's a third group: prospective customers. Sometimes people consider how recently, how frequently, or what kind of changes are made as a factor in their product evaluation. I don't think there's currently a way to give these people access to the changelog - what would be ideal would be to show them a summary something like GitHub's change history grid, and/or maybe a list of changelog post headlines.
We also don't want our changelog to be public, meaning we don't want anyone to be able to see it who is not either a user of our application or one of our employees. (We found that Public enables anyone – including competitors – to find our changelog via Google or other search engine.) But we can only apply one privacy rule, so we can't differentiate customer-facing change announcements from internal announcements.
C
Cloudy Swift
It's indeed really missing in our use case.
We choose Canny in the first place because we were able to have separate boards for our teams requesting internal tools updates... and for our clients that should not see such internal discussions.
Unfortunately, we can't communicate properly to both our audiences because this distinction do not exist in the changelog.
We currently have to rely on Google Site for publishing internal product updates 🤯
H
Harlequin Wombat
Yes yes! 🙌🏼
T
Thorough Swan
This would be really nice; we manage this with a dedicated Slack channel but would be nice to have internal and external updates in the same place.