From the workshop
Notes from the workshop.
What we learn building Forge apps, and what we keep having to explain twice. Mostly about knowing what your Atlassian work costs, keeping Confluence governable, and keeping Jira configuration from quietly rotting.
Jira's 700 custom field limit is not a site-wide cap
Jira Cloud caps custom fields at 700 per space, not across your whole site, and one field can count toward several spaces at once. What Atlassian's guardrails actually say, what happens when a space reaches the line, and the order to audit in.
How to choose a cost tracking app for Jira
A buying guide written by the team behind OnBudget. Six criteria phrased as questions a buyer would ask, a table comparing five approaches rather than five products, and a plain account of where OnBudget fits and where it does not.
What does your Jira work actually cost?
Jira records what your teams did. It does not record what it cost. Here are the five signals most teams already have, how to turn each one into money, and how to tell which of them your data can actually support.
Pay for the 20% You Use: Shrinking Your Atlassian App Footprint Without Losing the Workflow
Most Atlassian Marketplace bills pay for features nobody uses. An honest usage audit and a focused custom Forge app turn pay-per-seat-forever into pay-once-you-own-it, with a better fit for your team.
Atlassian Team '26: What We Expect, Think, and Hope Ahead
From the perspective of an Atlassian Marketplace partner building integrations every day. What we're watching for at Team '26: AI in the workflow, the System of Work, enterprise needs, and where partners still matter.