Hypothetically, how would you feel about an aggregated changelog, similar in nature to the Forge changelog, but containing all Atlassian cloud product and platform changes?
Yeah, that would work as long as you make sure that the bespoke solution & post guidelines are tweaked to support long-format to at least contain a description and link(s) to relevant content, change logs & documentation.
As an example, how would any of these posts be delivered in a world of separated content & announcement?
- Updated: 31 January 2022 - Action required - Deprecating persistent refresh tokens
- New Jira workflow condition module in Forge
- Preparing for Confluence 8.0 - EAP coming soon
To be a bit more realistic, let’s say “all Atlassian cloud product and platform changes to APIs or otherwise anticipated to have an impact on apps or partners”
Yes, that makes sense.
EDIT:
One example of an announcement going wrong is this Introduing Content State API. There are three separate posts with three different cross-references, none of them linking directly to each other. That would still require listening to multiple channels to get the full picture.