Jira Sandbox to Prod Project Configuration Merger

Inspiration

Managing project configurations in Jira across environments (Sandbox/Production) is often tedious and error-prone when done manually. Inspired by the need for automation and consistency, we set out to streamline this process. Atlassian currently offers tools to copy projects, but only if they don’t already exist on the destination instance. For teams testing configurations in a sandbox environment, manually replicating settings to production is time-consuming and prone to errors. Existing solutions also lack support for merging configurations across environments. This gap drove the creation of our app, designed to save time, reduce errors, and bring efficiency to Jira configuration management.

What it does

The Jira Sandbox to Prod Project Configuration Merger automates the transfer of project configurations from a Sandbox environment to Production. It handles existing projects seamlessly, eliminating manual intervention and reducing errors.

How we built it

We utilized Atlassian's REST API to extract, compare, and deploy project configurations. The app leverages scripting in Forge (JavaScript) to automate configuration merges, with a focus on user-friendly execution and robust error handling.

Challenges we ran into

Unable to execute REST Call to different instances
You need to call a lot REST APIs to read the current config.
Limits of API and execution times in Forge
Ensuring compatibility with Atlassian’s API rate limits and authentication mechanisms.

Accomplishments that we're proud of

Successfully building the first POV which can execute the first actions
Delivering a tool that can save hours of manual effort and boosts operational efficiency.