validating Structures migrated into Cloud environment => filters missing, settings missing

[Josef Schiessbühl]

Hello,

may I kindly ask you if there is a kind of guideline or maybe it is foreseen that way:
We are asked to validate structures after a migration into Jira -Test Cloud env.

The structures display in the most cases in their import filters the filters via filterid (e.g. filter=123456 instead of filter='Importfilter Structure A'
Thus I would assume to prepare before via filtername and somewhere and somehow to migrate in bulk the dedicated filters... how is this foreseen? if yes where can I find a documentation?

The so called migrated structures do not have any information concerning extensions and other rules from Automation such as Extend Linktypes, sort etc. everything available in Jira Datacenter not anymore or any longer in Structure. Do we have to add that manually for every structure or is there an automatic way foreseen?
Many thanks.
kind rgds
Josef

[Stepan]

Hello @Josef Schiessbühl 

Please note - generators(the Automation feature) are migrated, since most of them exist in Structure Cloud. We have an extensive migration-related documentation that covers a lot of information regarding the feature parity, the preparation of structures, and what to expect when migrating specific features. We strongly recommend going through it; you might find a lot of answers to your questions there.

If a migrated structure appears empty, then it's worth checking that its generators are not hidden (there is a button for this in the top-left corner of any structure), and if the generators are there but they don't add anything, then it's likely related either to the structure owner's access to items in Jira or lack of it, or the absence of the referenced items on the Jira instance. 

As for the saved filters - filters indeed are referenced by IDs. If the filter's ID changes on the Cloud instance, then the reference is expected to break. You would need to adjust the generators with such filters and replace the filters with the relevant ones.

I hope this helps. If you need any additional assistance with migration, please reach out to us directly at our support portal, and we'll take a look at your structures in more detail.

Best regards,
Stepan
Tempo (the Structure app vendor)

[Josef Schiessbühl]

Hello Stepan,
many thanks for your prompt answer, much appreciated.

a) Filters:
If we use only filternames - can we copy/migrate them automatically to Jira.

b) Filternames in Structure
And if we use only filternames in structure and basically if the importfilter were okay I also would expect that the generators are imported. Is this the case? Or do you have to add them always manually for every structure?

What is your experience? What your advice?
Thnx in advance.
kind rgds

Josef

[Josef Schiessbühl]

Hi, 

what else was/is missing are the quickfilters...
probably the non-trigger of them also the false filter-id...?

many thanks

Josef

[Stepan]

If a saved filter is referenced in a generator, and the generator is migrated, it depends on whether the same saved filter exists in Jira Cloud. If it does, and it has the same name, then the generator in the structure will work the same after the migration. But in any case, the generator itself will be migrated along with the JQL query it has. 

Please note - migrating a generator that has a saved filter referenced in it doesn't mean that the saved filter itself is migrated in Jira. Structure only has a reference to it; the filter has to be migrated separately along with the rest of Jira data.

As I mentioned above, you can submit a support request at our portal, and share details of your structures/setup/migration before and after, and we'll be glad to take a look, and share insights if anything is missing there. Migration is a complex process, and answers to some questions depend heavily on how the migration is performed, the scope of it, and other elements. It would be much easier for us to assist you if we had a better understanding of what you have and what took place exactly.

Best regards,
Stepan