Discussions
-
How do you support users (and keep Jira usable). What’s working right now?
I’d love to kick off a proper admin-to-admin discussion on something we all deal with, but rarely document: supporting Jira users in a way that improves adoption without turning Jira into bureaucracy. Most of the day-to-day friction in Jira isn’t caused by “bad users”. It’s caused by a gap between what the tool can do and…
-
Atlassian is getting more powerful… and more complex. The “keep it simple” paradox
I’ve been working with Atlassian tools long enough to notice a pattern: every year the platform gets more capable, more integrated, and more “enterprise-ready”… and at the same time it gets harder to keep the day-to-day experience simple for normal users. It’s not a complaint post. It’s more of an observation and a paradox…
-
The Atlassian App Paradox (Partner Edition): We sell “outcomes”… but we inherit the complexity
If you’re an Atlassian partner (or you work closely with partners), you’ve probably felt this tension: Customers want faster delivery, cleaner processes, better reporting, stronger governance and they want it yesterday.Atlassian keeps shipping powerful new capabilities plus a Marketplace that can fill almost any gap.So we…
-
Confluence Cloud “New Editor”: what’s actually changing (and how to survive it)
If you’ve noticed legacy pages suddenly flipping to the new Cloud editor: you’re not imagining it. Atlassian is actively phasing out the legacy editor so Confluence Cloud runs on one single editing experience going forward. Why it feels “sudden” For years Confluence Cloud has lived in two worlds: older pages created in the…
-
Scroll Documents and Latex Math - K15t and Appfire
Here I wanna give some praise and Kudos for @K15t GmbH and @Appfire Support Some background: After migrating Scroll Documents into Forge from K15t, exports from Scroll Documents that included LaTeX math from Appfire (we use Scroll Documents for our product documentation) were broken and stopped rendering Properly. Both…
