Unable to import dashboards to a new system if the dashboard has a filter

[engineering-issue-sync-app[bot]]

Describe the bug

It is not possible to import and exported dashboard that contains variable filters into a new system. The user always gets a warning about missing variables.

Hint: This might be caused by us first validating everything, including dashbaord filters, and then importing everything. The dashboard filter validation seems to be checking report data based on ID, by the time this validation happens the reports arent saved yet.

Expected behaviour

If variable filters exist on a dashboard and the variables exist in the data of the reports on the dashboard in the target system, it should be possible to import the dashboard without errors.

To Reproduce

Steps to Reproduce the issue:

Create a dashboard and add a variable filter Export the dashboard to a JSON file Start a new empty instance of Elasticsearch but still connected to the same C7 system Re-create the same dashboard with the same filter but with a new name. Try to import the original JSON dashboard, you will get an error and it will not import, in the har file it reports an invalid filter

Environment observed:

• Optimize mode(s): C7
• Optimize version(s): 3.8.1, 3.13.2
• Database(s) (Elasticsearch/OpenSearch): ES

Links

https://jira.camunda.com/browse/SUPPORT-22330

### Pull Requests

Bug Lifecycle

For managing the issue lifecycle, please use the workflow commands. You can see the available commands by writing /help as a comment on this issue.

QA Verification

Is this bug reproducible?

• [ ] Yes. If so:
  • [ ] The bug description is clear
  • [ ] The steps to reproduce are clear
  • [ ] The environments observed are correct and complete
• [ ] No

Review

Review Resources

• Feature PR: {Link to PR targeting the main branch}
• Preview environments: {Link(s) to preview environments}

Engineering Review

• [ ] All code targeting the main branch has been reviewed by at least one Engineer
• [ ] The PR targeting the main branch has been approved by the reviewing Engineer
• [ ] If the API has changed, the API documentation is updated
• [ ] All other PRs (docs, controller etc.) in the breakdown have been approved

QA Review

• [ ] The change is implemented as described on all target environments/versions/modes
• [ ] The documentation changes are as expected

Completion

• [ ] All Review stages are successfully completed
• [ ] All associated PRs are merged to the main branch(es) and maintenance branches
• [ ] The correct version labels are applied to the issue

^{:robot: This issue is automatically synced from: source}