You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected module
Does it impact the UI, backend or Ingestion Framework?
--Backend
Describe the bug
A clear and concise description of what the bug is.
-- Relating data assets from a sub-domain not working / consistent within "Domain" view but working from "Data asset" view
In other words if I enter any data asset and have permissions (Admin access to all) > I can relate the data asset to a sub-domain
If I however within "Domain" feature > Navigate to sub-domain > press "Relate assets" > I can only relate assets that are part of my Parent domain
To Reproduce
Screenshots or steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
--A user with full permissions should be able to related any data asset to a sub-domain through the "Domain" navigation.
The behavior should be consistent no matter what interface you use to relate data assets to domains
Affected module
Does it impact the UI, backend or Ingestion Framework?
--Backend
Describe the bug
A clear and concise description of what the bug is.
-- Relating data assets from a sub-domain not working / consistent within "Domain" view but working from "Data asset" view
In other words if I enter any data asset and have permissions (Admin access to all) > I can relate the data asset to a sub-domain
If I however within "Domain" feature > Navigate to sub-domain > press "Relate assets" > I can only relate assets that are part of my Parent domain
To Reproduce
Screenshots or steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
--A user with full permissions should be able to related any data asset to a sub-domain through the "Domain" navigation.
The behavior should be consistent no matter what interface you use to relate data assets to domains
Version:
openmetadata-ingestion[docker]==XYZ
]Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: