From internal tool to Marketplace: How ScriptFabric built on Forge
ScriptFabric transitioned from an internal Jira scripting tool to a Marketplace app by leveraging Atlassian’s Forge platform, replacing Groovy with JavaScript and TypeScript for broader accessibility.
ScriptFabric originated as an internal solution at Canarys Automations Limited to address the team’s need for more accessible Jira scripting using JavaScript instead of Groovy. The developers chose Forge for its managed platform, which handled infrastructure, authentication, and permissions, allowing them to focus on the scripting experience rather than platform maintenance. Their goal was to make scripting in Jira more approachable for teams already familiar with modern JavaScript workflows, removing the barrier of specialized Groovy expertise.
The ScriptFabric team initially explored Forge’s documentation but found the mental model clearer only after completing the full development cycle—learning, developing, deploying, testing, and iterating. They emphasized the value of starting with a small end-to-end app to build a practical understanding of Forge’s lifecycle, rather than attempting to master the platform through theory alone. This hands-on approach helped them navigate local development, tunneling, and deployment within Atlassian sites more effectively.
Publishing ScriptFabric to the Marketplace revealed both advantages and challenges. The Forge manifest simplified connections to the Atlassian ecosystem, reducing the need for custom infrastructure. However, the team encountered friction in the publishing process and worked through issues with Atlassian, providing actionable feedback to improve the platform. Their experience highlights that internal tools can evolve into broader solutions when a shared problem is identified, though transitioning to Marketplace requires additional considerations like pricing, positioning, and onboarding.
ScriptFabric’s journey did not end with its Marketplace launch; it opened new opportunities, including deeper integrations with developer tools like GitHub and Bitbucket, and exploring AI-driven features to make scripting more accessible. The team is also focused on helping teams migrate existing Groovy workflows to JavaScript. Their advice to other developers is to start with the smallest viable Forge app that completes the full lifecycle, then expand based on user needs and technical requirements.