@Josh Golosinskiy Lol I hear ya. The official site at the link below has all release notes but I’m hoping to find something that’s focused more on major/impactful changes. https://confluence.atlassian.com/cloud/blog I subscribed to several Atlassian forums but now my inbox is flooded with emails!

@Josh Golosinskiy will the recordings be made available to premium members afterwards?

@Josh Golosinskiy awesome, thanks!

This reminded me of one of @Josh Golosinskiy’s posts which ended with: I never recommend a plugin until we’ve fully tapped Jira’s native potential. Because the real question is simple: 👉 Will this plugin pay for itself? If the ROI isn’t clear, you’re just adding risk, cost, and complexity. Sure, some apps are amazing. And yes, some partners will swear you need their plugin. (Remember, they’re selling.) But Jira was built to work out-of-box. Don’t let the noise distract you from mastering the tools you already have. Keep it lean. Keep it native. Then—and only then—ask what’s missing. https://www.linkedin.com/posts/joshgolosinskiy_atlassiancreator-jira-plugins-activity-7325549298371174400-yKAI

@Josh Golosinskiy Agreed on avoiding friction as much as possible but it depends? Comments should be required on done/resolved status for certain request types that aren’t incidents or bugs, as it’s usually obvious when incidents and bugs are resolved (but should still have internal/agent comments and Confluence notes capturing how). For example, customers asking help desk questions or similar requests should be getting answers in JSM comments, not via email or slack. Or it should at least be noted they were provided response X on platform Y/email. Good for an audit trail too.