/
Migrating GO! JQL from Atlassian Connect to Forge: Steps for Administrators and End Users

Migrating GO! JQL from Atlassian Connect to Forge: Steps for Administrators and End Users

Action required before getting started: The Forge version of GO! JQL will not be applied automatically. A Jira administrator must manually update the app via the Atlassian Marketplace before any migration steps can be taken.

πŸ—“οΈ Important deadline: The Connect version of GO! JQL will be permanently removed on June 1, 2026. After this date, the old version will no longer be available. Please ensure the migration is completed before this date to avoid any disruption.

Product: GO! JQL

Audience: Jira Administrators & End Users
Version: Forge Release

Overview

GO! JQL has been migrated from the Atlassian Connect platform to Forge β€” Atlassian’s modern, secure, and long-term supported app infrastructure. Atlassian announced deprecation of Connect and its future support. This guide explains what changed, what actions are required from administrators and end users, and how to migrate saved Extended Search filters to the new Forge version.

Summary: Admins must update the app to Forge and perform a one-time export/import of Extended Search filters. End users will then verify filters and, if applicable, replace deprecated dashboard gadgets with new Forge gadgets.

What’s Changing?

Area

Connect (Old)

Forge (New)

Area

Connect (Old)

Forge (New)

Platform

Atlassian Connect

Atlassian Forge

Atlassian Support

Being deprecated

Long-term supported

Extended Search Filters

Saved in old panel; require admin export

Available after admin import into Forge panel

Dashboard Gadgets

Connect gadgets (deprecated)

New Forge gadgets required

For Jira Administrators

The following steps must be completed by a Jira administrator. End users do not need to take any action until the administrator confirms the migration is complete.

Step 1 β€” Update the App

  1. Go to Jira Settings β†’ Apps β†’ Manage Apps.

  2. Find GO! JQL in the installed apps list.

  3. Update to the latest Forge version via the Atlassian Marketplace.

  4. Confirm the installation is complete before proceeding.

Do not proceed to Step 2 until the Forge version is successfully installed.

Step 2 β€” Migrate All Filters (One-Time Action)

Export all saved Extended Search filters from the old Connect version and import them into the new Forge version in a single action. This covers all users; individuals do not need to perform this step.

  1. Open the old (Connect) GO! JQL Extended Search panel.

  2. Click Export to download the filters file.

  3. Open the new (Forge) GO! JQL Extended Search panel.

  4. Click Import and upload the exported file.

πŸŽ₯ See the video below for a step-by-step demonstration of the export and import process.

Once imported, all filters will be immediately available to all users in the new Forge Extended Search panel.

Step 3 β€” Notify Users

Once the migration is complete, inform your users so they can verify their filters and update their dashboards if needed.

For End Users

You do not need to export or import any filters yourself. Your Jira administrator will handle the migration on your behalf. After confirmation from your administrator, follow the steps below.

Step 1 β€” Wait for Admin Confirmation

No action is required until your Jira administrator confirms the app update and filter migration are complete.

Step 2 β€” Verify Your Filters

  • Open GO! JQL Extended Search in Jira.

  • Confirm all your previously saved filters are visible.

  • If any filters are missing, contact your Jira administrator.

Step 3 β€” Update Your Dashboards (if applicable)

If you use GO! JQL gadgets on Jira dashboards, the old Connect gadgets will no longer work after the migration. Replace them with the new Forge gadgets.

  • Open the affected Jira dashboard.

  • Remove the deprecated Connect GO! JQL gadgets.

  • Add the new Forge versions of the GO! JQL gadgets.

  • Reassign your filters to the new gadgets.

πŸŽ₯ Video Walkthrough β€” Filter Export & Import

GOJQLFORGE.mp4

Best Practices & Notes

  • Complete the export/import soon after updating to Forge to ensure continuity of user filters.

  • Keep the exported file in a secure location and delete it when no longer needed.

  • Plan a brief maintenance window to update gadgets on critical dashboards.

  • After import, spot-check a few complex filters (e.g., with functions or custom fields) to validate results.

Troubleshooting

Confirm the app is updated to the Forge release and that the file is the unmodified export from the Connect panel. Try again with a fresh export. If the problem persists, contact GO! JQL support with the error message.

Verify that the import completed successfully and that users are opening the Forge Extended Search panel. If only some filters are missing, re-run export/import and advise users to refresh their browser cache.

FAQ

No. The Jira administrator performs a single export from the old Connect panel and a single import into the new Forge panel. This covers all users.

Not if the administrator completes the export/import before removing the Connect version. Perform Step 2 promptly after the update to prevent loss.

The old Connect gadgets are deprecated and will stop working after migration. Each user must manually replace them with the new Forge versions and reassign their filters.

Contact your Jira administrator first. For product-related issues, reach out to the GO! JQL support team. β†’ https://almbase.atlassian.net/servicedesk/customer/portal/4

If you need assistance with a specific migration scenario (large instances, audit requirements, or rollback considerations), contact the GO!