Structure Cloud: Equivalent of Server/DC Filter + Insert behavior after migration?

Question

Hello,

we recently migrated from Jira Data Center to Jira Cloud, and we are trying to reproduce the behavior of one of our existing Structures.

On Structure for Jira Data Center, we had the following generator configuration:

* Filter: project = "Capability Management and assignee=..."
* Insert: issuetype = Demand

This configuration did not insert all Demand issues. Instead, it only inserted Demand issues that were related (via our custom Demand Link) to issues in the Capability Management project.

After migrating to Structure Cloud, the exact same configuration inserts all Demand issues, regardless of whether they are linked to Capability Management issues.

My questions are:

* Is this a known behavioral difference between Structure Data Center and Structure Cloud?
* Was this functionality intentionally removed or changed in Cloud?
* Is there an equivalent generator configuration in Structure Cloud that reproduces the same behavior without using additional Jira automation, labels, or third-party JQL extensions?

For clarification:

* We use a custom issue link called Demand Link.
* A Demand can be linked to issues from different projects.
* We only want to display Demands that are linked to issues in the Capability Management project.

Any guidance would be greatly appreciated.

Thank you!

Andreoli_ Dr_ Christophe · Answer

ok thank you, I will do it

Stepan Kholodov · Answer

There is no difference in how Insert and Filter generators work in Structure Cloud compared to Data Center: just the same, inserters add work items that match a given JQL query, and the filters reduce the scope of these items based on their configured queries. If you're seeing different results in a structure in Cloud using the same exact generators, then something else is causing the discrepancy.

I suggest you create a support request at our portal, share screenshots of your Data Center structure and your Cloud structure so we can see how both are currently built, and share what's missing/what you'd like to be different. Once we understand your setups, we'll be able to provide more useful information.

Best regards,
Stepan

Andreoli_ Dr_ Christophe · Answer

Thank you, Stepan.

I think my question may have been misunderstood. I am not asking about the migration itself.

My question is specifically about the interaction between the Filter and Insert generators in Structure Cloud.

In Structure Data Center, our configuration effectively worked as follows:

Filter: project = "Capability Management" AND assignee = ...
Insert: issuetype = Demand

The Insert generator did not simply insert every Demand matching issuetype = Demand. In combination with the Filter and our Demand Link, only the relevant Demands linked to the filtered Capability Management issues were displayed.

My question is therefore:

Does Structure Cloud support the same interaction between Filter and Insert generators as Structure Data Center, or do Insert and Filter behave differently in Cloud?

If they behave differently, is there a native Structure Cloud equivalent that allows us to insert only Demands linked via Demand Link to the filtered Capability Management issues?

I am specifically looking for a solution using Structure generators, without Jira Automation, labels, or third-party JQL extensions.

Thank you.