ScriptFabric and the Evolution of Jira Automation: How Canarys Automations Leveraged Atlassian Forge to Bridge the JavaScript Gap

The landscape of enterprise project management and automation is undergoing a significant shift as development teams increasingly prioritize modern programming languages over legacy specialized scripts. A primary example of this transition is the emergence of ScriptFabric, a new Atlassian Marketplace application designed to modernize Jira scripting. Developed by Canarys Automations Limited, ScriptFabric was born from a common internal bottleneck: the reliance on Groovy for Jira automation, a language that, while powerful, often sits outside the primary skill set of modern JavaScript and TypeScript developers. By utilizing Atlassian’s Forge platform, the team at Canarys has successfully transformed a localized solution into a scalable product, signaling a broader trend in how internal tools are being commercialized within the Atlassian ecosystem.

The genesis of ScriptFabric is rooted in a challenge familiar to many IT and software development organizations. Within the Jira environment, scripting and automation are essential for extending the platform’s native capabilities, yet for years, the dominant language for these tasks has been Groovy. While Groovy is a robust JVM-based language, the modern development workforce is overwhelmingly proficient in JavaScript and TypeScript. This disparity creates a "specialization gap," where teams that are perfectly capable of building complex web applications are forced to seek out niche expertise just to automate a workflow or create a custom listener in Jira. Hoysala Garudanagiri and Sandeep Kuruva, key members of the development team at Canarys Automations, recognized that this friction was not just a minor inconvenience but a barrier to efficiency. Their goal was to create a tool that allowed developers to interact with Jira using the modern JavaScript workflows they already use daily.

Choosing the right foundation for such a tool was critical. The team ultimately selected Atlassian Forge, a managed development platform designed to simplify how developers build, host, and run apps for Atlassian products. Unlike the older "Connect" model, which required developers to manage their own servers, databases, and security protocols, Forge offers a serverless environment where Atlassian handles the underlying infrastructure. For the ScriptFabric team, this was a decisive factor. Forge’s managed nature meant that the team did not have to spend months building "plumbing"—such as authentication, hosting, and permissions management—before they could begin working on the core logic of their application. By leveraging Forge’s built-in capabilities, they were able to focus exclusively on the user experience and the integration of the JavaScript ecosystem into the Jira interface.

The development process for ScriptFabric was characterized by an iterative, hands-on approach rather than a purely theoretical one. According to the development team, the mental model for building on Forge only truly solidified once they moved through a complete development cycle. This cycle—learning the documentation, developing a prototype, deploying to a test environment, and refining based on real-world results—proved more effective than extensive pre-study. Sandeep Kuruva noted that the team’s journey was defined by "actually shipping something," rather than just learning about the platform in a vacuum. This "ship-to-learn" philosophy is becoming a standard recommendation for developers entering the Forge ecosystem. The ability to use "tunneling"—a Forge feature that allows developers to run code locally while it interacts with a live Atlassian site—was cited as a major advantage in speeding up this feedback loop.

As the project progressed, the team experimented with various development paths offered by Atlassian, including Forge Studio. Forge Studio is often seen as an entry point for rapid prototyping, allowing developers to see tangible results quickly without getting bogged down in complex configurations. However, as ScriptFabric grew from a simple internal tool into a feature-rich product intended for the global Marketplace, the team transitioned to the Forge Command Line Interface (CLI). This progression highlights a vital aspect of the Forge ecosystem: it is designed to scale with the complexity of the application. Developers can start with the fastest path to a proof-of-concept and then migrate to more robust, traditional development workflows as the application’s requirements expand.

Despite the advantages of a managed platform, the journey was not without its hurdles. The team encountered "sharp edges" during the publishing process on the Atlassian Marketplace. Navigating the final steps of commercialization required close collaboration with Atlassian to resolve technical and procedural issues. This experience serves as a reminder that building a successful application involves more than just writing functional code; it requires navigating the complexities of a commercial ecosystem. However, the ScriptFabric team viewed these challenges as opportunities to provide feedback to Atlassian, helping to refine the platform for future developers.

The transition of ScriptFabric from an internal solution to a commercial Marketplace product illustrates a growing pattern in the tech industry. Many successful SaaS products begin as a solution to a specific team’s "annoying problem." In the case of Canarys Automations, they realized that if their own developers were struggling with the Groovy-centric nature of Jira automation, thousands of other teams likely faced the same issue. Moving from a tool to a product required a shift in mindset. The team had to move beyond code functionality to consider packaging, pricing models, competitive positioning, and the onboarding experience for users who had no prior context of the tool’s development. This transition forced them to think like product builders, ensuring that the value proposition of ScriptFabric—making Jira scripting accessible to the JavaScript community—was clear and immediate.

The technical impact of ScriptFabric lies in its ability to democratize Jira customization. By providing a familiar environment for JavaScript and TypeScript, it lowers the barrier to entry for junior and mid-level developers who may not have legacy JVM experience. This has the potential to accelerate digital transformation within organizations, as more team members become capable of contributing to automation efforts. Furthermore, the use of TypeScript brings the benefits of static typing and better tooling support to the world of Jira scripting, reducing the likelihood of runtime errors in critical business workflows.

Looking ahead, the roadmap for ScriptFabric is ambitious. The team is currently exploring deeper integrations with version control systems such as GitHub and Bitbucket, aiming to bridge the gap between Jira automation and the broader DevOps toolchain. Perhaps most significantly, they are investigating the role of Artificial Intelligence in the scripting process. The goal is to create an experience where a developer can describe a desired automation in natural language, and ScriptFabric, powered by AI, will generate the corresponding JavaScript code. This move aligns with broader industry trends toward "low-code" and "AI-assisted" development, further lowering the barrier to entry for Jira customization. Additionally, the team is focused on creating migration paths for organizations looking to move their existing Groovy-based scripts into the more modern JavaScript/Forge environment.

For developers and organizations considering building on the Forge platform, the ScriptFabric story offers several practical takeaways. The most prominent advice from the Canarys team is to start with the smallest possible version of an idea and take it through the entire lifecycle—from manifest creation to deployment and testing. Establishing this foundation early allows developers to understand the relationship between permissions, modules, and the Atlassian site before tackling more complex features. The success of ScriptFabric suggests that the Atlassian Marketplace remains a fertile ground for developers who can identify a real friction point and solve it using modern, accessible technologies.

In conclusion, ScriptFabric represents more than just a new tool for Jira; it is a case study in the modernization of the Atlassian ecosystem. By choosing JavaScript over Groovy and Forge over self-managed infrastructure, Canarys Automations has aligned itself with the future of enterprise software development. Their journey from solving an internal frustration to launching a global product underscores the value of the "problem-first" approach to software creation. As the platform continues to evolve with AI and deeper integrations, ScriptFabric is positioned to play a central role in how teams automate and extend their Jira experiences in the years to come.