Feels like a broken record - is it even possible to move insight data between cloud instances?

[Tyler Gibson]

At this point I'm giving up hope on Insights, but I'm hitting yet another extremely basic problem -

We have a sandbox Jira instance and a production Jira instance - both cloud.

When working with an Insight schema - how in the world can you export/import at any level from one cloud instance to another?  

I have tried using "Export Objects" but no matter what I do, they do not preserve referenced object fields.  Which defeats the entire purpose of export and import.

Is this possible?  For IT Admins here - how in the world do you manage Jira instances to isolate changes into production? I feel like I must be missing some major part of the ecosystem here, or is Jira Cloud just not actually ready for any company to use in production?

[Felix Haverkamp]

This video states that there is a export/import option for insight schemas, but i think its remove from cloud with the new landing page for insight.
Currently insight is not really useful and lacking so many loved features from the server / datacenter.

https://www.youtube.com/watch?v=RDZ3_vzy3Dg

if you try to acess the url

https://INSTANCE.atlassian.net/jira/servicedesk/insight/configure?tab=imports

you get redirected to insight default view ....

@Insight Team, could you fix that?

[SUNMI HELP DESK]

你好

[Joseph Chung Yin]

@Tyler Gibson -

Unfortunately, it is not possible to export Insight Schema in the Cloud env as far as I know.  There is an outstanding enhancement request - https://jira.atlassian.com/browse/JSDCLOUD-9967.

Schema level export/import is only available right now for Jira Data Center (on-prems) env.  Even in the on-prems env, there are still bugs when one tries to export an Insight schema from one instance and using the export zip as an import in a different env + even within the same instance.  

Example - The source schema cannot have any required attributes sourcing from different object types (if you want your export zip contains all the objects).  It is because the import process (using the export zip) will fail to import all the object due to a racing condition problem.  The problem essentially cannot process all the source objects first where they are required attributes of other objects.  Hope this makes sense.

The only option I can think of for the Cloud env is to create the empty schema in your prod instance and configure it same as what you have in another instance.  Afterward export your objects from the other instance and import them into your prod env's schema.  It is MANUAL and I don't like it at all... 

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

[Tyler Gibson]

This is also a complete showstopper.  We have to change EVERY attributeID, objectID, schemaID, between the two environments.  Issues with insight fields cannot be migrated either or their are permanently in a broken state because the workspace ID's dont match.

All automations break.  All UI breaks that references any of these.