Three features to improve the way you migrate your apps to cloud

[#1]

Hi Atlassian Community,

My name is Lydia Buck, and I’m a Product Marketing Manager on the App Migrations Platform Team. I’m excited to share three features we’ve developed to improve your overall app migration experience based on your feedback.

Understand Insights with App Usage for Jira

We’ve heard from you that occasionally app migrations can take longer than expected due to low visibility into app usage. This makes it difficult to make quick decisions about whether an app is needed in cloud or not. Also, we’ve heard that sometimes your teams are unable to understand your app data footprint in your on-premise instances which can lead to a drawn-out app assessment experience. Determining app usage can be done manually, however, we know that that process can be time-consuming for your teams. Therefore, we’ve developed App Usage for Jira on the Atlassian Marketplace to help resolve these concerns and provide automated app usage insights.

App Usage for Jira helps you evaluate your apps and ensure your team has a clear understanding of how apps are being used in your instance, where, and with what frequency. These details are visible through data points such as;

• Tracking custom fields

• Workflows

• Database tables

• JQL functions

• REST API usage

• Page views

• Dashboards added by your apps

Insights from this app will allow your organization to conduct a more efficient app assessment because your team will have additional intel about what apps are being used and when. Ultimately, this will help determine which apps need to be prioritized during your migration based on how business-critical they are for your organization.

Restart the Migration of a Specific App with App Re-Run

Sometimes app migrations can fail due to unforeseen circumstances like network issues or busy resources. This can be frustrating because one failed app migration means that your team will likely have to restart the entire migration. This requires re-migrating the core product (Jira or Confluence) plus any other apps that succeeded in the original transfer. To remedy this we’ve developed a feature called App Re-Run.

With the addition of this feature, you can restart the migration of a specific app within the Cloud Migration Assistants (CMAs) without having to redo the entire migration. This capability can be found in the app migration progress table and is helpful when it comes to troubleshooting or making a specific adjustment to the migration of an app. Instead of having to restart the entire migration to make adjustments, you’re able to re-run the migration for the specific app that’s blocked and continue on with your migration.

Stop an In-Flight App Migration with Cancel App Migration

Last, we want to empower you to take action if your app migration gets stuck, your team should be able to take action if your app migration isn’t progressing in a timely fashion and be able to Cancel an App Migration if necessary.

This self-serve feature within the CMAs will give you the ability to cancel or stop an in-flight ('In progress' status) app migration if it seems to be taking too long, appears to be stuck, or if you’ve changed your mind about migrating that app. You can find the cancel option under the actions column of the app migration progress table within app migration section of the CMAs. Ultimately, this feature gives your team better control over your app migration, and canceling a specific app will not affect the progress of any other apps you have in the migration.

Ready to try it out?

• App Re-Run and Cancel App Migration are currently live for Confluence Cloud Migration Assistant v3.4.14 and above, as well as Jira Cloud Migration Assistant v1.9.17 and above.

• App Usage for Jira is available Jira Server 8.20.0 - 9.11.3, Jira Data Center 8.20.0 - 9.12.1.

We hope you enjoy these features! Leave any feedback below in the comments and stay tuned for more features to improve the app migration experience coming soon!

[Rob Little]

Hello Folks.

We are trying to guide a client through installing this on their server install, but there is no apparent way to obtain this for server.  Can someone clarify please?
Can we use the DC obr file, and upload it to the clients manage apps screen on their server install? 

thanks in advance

Rob

[Hariharan Rajendran]

Hi @Rob Little ,

I understand your question is about installing App Usage for Jira in a Jira Server instance. I see that App Usage for Jira is available for Jira Server from 13/Sep/2023 (marketplace listing).

If you are not able to find and install App Usage for Jira  from marketplace via Manage Apps (UPM) screen in your Jira Server, you can download App Usage for Jira OBR for Jira Server from here and upload it via Upload App option in Manage Apps (UPM) screen.

Thanks