ScriptFabric began as an internal tool built by the Canarys Automations team to make Jira scripting accessible via JavaScript/TypeScript instead of requiring Groovy expertise. The team chose Atlassian Forge for its managed platform (handling auth, hosting, and Jira integration) and learned it by shipping a small app through the full development lifecycle rather than studying docs first. They started prototyping in Forge Studio before graduating to the Forge CLI as the product matured, hit friction during the Marketplace publishing process, and eventually turned the internal solution into a full Marketplace product. Future plans include GitHub/Bitbucket integrations and AI-assisted script generation.
Table of contents
TL;DRThe Origin StoryChoosing Forge (and JavaScript)You learn Forge by actually shipping somethingStart with the fastest path and graduate when you need toWhat surprised them about building on ForgeThe moment an internal tool becomes a productWhere ScriptFabric goes nextIf you’re thinking about building on Forge586 Impressions