Git Integration not supporting Report import if linked Semantic Model resides in separate workspace

[Mary_Kelsch]

We have shared semantic models residing in a separate workspace from multiple associated reports, which is a common practice for many teams in our company.  We also have Git Integration turned on for the workspaces and have a respective workspace for dev/qa/prod environments.  For instance:
- "Workspace A Dev" housing dev version of "Report I" and "Report II"

- "Workspace B Dev" housing dev version of "Semantic Model" which is linked to both Report I and Report II

- "Workspace A QA" will house qa version of "Report I" and "Report II"

- "Workspace B QA" will house qa version of "Semantic Model" which will be linked to the qa version of Report I and Report II

- All 4 workspaces are linked to their respective Git repositories

Once we deploy the semantic model and the associated reports from dev repositories to the qa repositories ("Workspace A Dev" to "Workspace A QA", "Workspace B Dev" to "Workspace B QA"), we can sync the semantic model into the "Workspace B QA" from the Git repo.  But when we tried to sync the reports from Git to "Workspace A QA", PBI throws an error stating "We weren't able to update this item because one of its dependencies can't be found".  This message is complaining that the associated semantic model is not present in the same workspace, even though it is present in another workspace, but the lineage is not maintained.

If we use PBI Deployment Pipeline, this is not a problem even though the semantic model and reports are in separate workspaces because the lineage is still kept.  What we are asking is to also make Git Integration support deployment using source code from lower env repo to higher env repo while keeping the Item Lineage, so we can pull down the Reports from Git repo without the associated Semantic Model being in the same workspace.