
Why your team's Confluence calendar is a table nobody updates
Open any mid-sized company Confluence instance and the page called "Q3 Events" is almost certainly a table. That is not a discipline problem - a table is a bad fit for the job.

Open any mid-sized company Confluence instance and the page called "Q3 Events" is almost certainly a table. That is not a discipline problem - a table is a bad fit for the job.

Some admin work is too complex to click through and too narrow to justify a Forge app. Script Console runs JavaScript against the Jira REST API from the browser, with a worked example: copying values between custom fields.

A flowchart takes three seconds to read. The same thing written as a paragraph takes three minutes. Mermaid puts the diagram in the page itself, so it stops drifting out of sync with the text.

User Macros never made the trip from Server to Cloud. The official replacement is a full Forge app, which is a sledgehammer for the small things teams keep asking for. Here is the middle ground.

Thirty stakeholders needed to track progress. Paying for 30 seats was a budget no-go, and guest accounts were an admin burden. Here is the Forge-based middle ground we shipped instead.

Atlassian Forge is becoming a paid platform, so we are introducing paid plans. Teams of up to 10 users keep using our apps for free, and nobody is forced to upgrade.