Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relating data assets to sub-domain not consistent / not working #19573

Closed
Prajwal214 opened this issue Jan 28, 2025 · 0 comments · Fixed by #19679
Closed

Relating data assets to sub-domain not consistent / not working #19573

Prajwal214 opened this issue Jan 28, 2025 · 0 comments · Fixed by #19679
Assignees
Labels
backend bug Something isn't working customer

Comments

@Prajwal214
Copy link
Contributor

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:

  • OS: [e.g. iOS]
  • Python version:
  • OpenMetadata version: [e.g. 0.8]
  • OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend bug Something isn't working customer
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants