🌐 Embracing the Cloud: Journey of Migrating Jira to the Cloud

Recently we decided to migrate our Jira to the Cloud.                                                                                       

Join us on our journey, where we faced and conquered challenges with innovative solutions for custom plugins, delivering remarkable outcomes.

🚀 Migration Challenges and Innovative Solutions in Jira Data Center

During the migration of our Jira Data Center instance, we encountered numerous difficulties that demanded new and innovative solutions to recreate our previous system. The process involved rewriting custom plugins in a restricted environment with limited resources.

🔧 Choosing the Right Development Platform

Initially, we had two options for the development platform: Connect and Forge. Connect offered a less restricted environment, while Forge provided the advantage of developing applications with existing hosting, multiple development environments, and built-in API authentication.

After careful consideration, we opted for Forge due to its provided hosting, which eliminated the need to maintain our own servers for running the plugins. However, this decision also meant facing certain quotas that we had to meet in order to run our apps in this system. Overcoming these quotas required out-of-the-box thinking and creative workarounds.

🎯 Recreating Essential Applications

We had to recreate three crucial applications during development:

  • An integration to send worklogs to our SAP system.
  • An importer tasked with processing an Excel sheet and creating 10,000 hours of worklog in Jira.
  • An issue panel containing a table with each row representing a linked issue, along with the ability to create a new one through the header.
  • Among these, the worklog importer proved to be the most challenging one.

💡 Overcoming Development Obstacles

One of the initial obstacles was the lack of a streamlined way to work on the code and test the same plugin in the same environment. Each developer had to create their own instance and test separately. To address this, we established a technical user that owns the plugins, granting access to all developers. Additionally, we utilized a sandbox environment within our current Cloud system.

🔍 Adapting to Quotas and Performance

The major challenge lay in adjusting our plugins to meet the quotas set by Forge. Especially with the worklog importer, it was daunting, as the original plugin took nearly six hours to validate and process records in the Data Center platform. In Forge’s environment, we had to come up with a solution involving cyclic invocations of functions that were limited to just 25 seconds.

Despite the significant difference from running functions without time limits, we persevered and managed to reduce the processing time to a remarkable 1.5 hours.

📈 Promising Results and Enhancements

So far, our end-user tests have shown promising outcomes. Not only have we successfully recreated our plugins in a new environment, but we have also achieved improvements in certain cases.

Join Us on the Journey

We are thrilled with the progress made during this migration journey, and we look forward to sharing more insights and updates with you. Together, we continue to embrace challenges and innovate, making our solutions even better.

Contact us: István Balog 📧 Email: istvan.balog@lupusconsulting.com 📞 Phone: +36 20/984 9687

Leave a Comment

Your email address will not be published. Required fields are marked *

GDPR Cookie Consent with Real Cookie Banner