Multi User/Team Ownership #17012
Assignees
Labels
Comments
harshach
added a commit
that referenced
this issue
Jul 14, 2024
harshach
added a commit
that referenced
this issue
Jul 14, 2024
|
As a user, I want to be able to add any combination of users and team as owners:
|
harshach
added a commit
that referenced
this issue
Jul 15, 2024
harshach
added a commit
that referenced
this issue
Jul 15, 2024
harshach
added a commit
that referenced
this issue
Jul 15, 2024
harshach
added a commit
that referenced
this issue
Jul 17, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 20, 2024
harshach
added a commit
that referenced
this issue
Jul 22, 2024
harshach
added a commit
that referenced
this issue
Jul 28, 2024
pmbrull
pushed a commit
that referenced
this issue
Jul 30, 2024
* Add multiple owners * Multi Ownership * Issue #17012: Multi User/Team Ownership * Issue #17012: Multi User/Team Ownership * Issue #17012: Multi User/Team Ownership - Fix Tests - Part 1 * Issue #17012: Multi User/Team Ownership - Fix Tests - Part 2 * Issue #17012: Multi User/Team Ownership - Fix Tests - Part 3 * Issue #17012: Multi User/Team Ownership - Fix Tests - Part 4 * Issue #17012: Multi User/Team Ownership - Fix Tests - Part 5 * Issue #17012: Multi User/Team Ownership - Fix Tests - Part 6 * Issue #17012: Multi User/Team Ownership - Fix Tests - Part 7 * Issue #17012: Multi User/Team Ownership - Fix Tests - Part 8 * Add Migrations for Owner Thread * update ingestion for multi owner * fix pytests * fixed checkstyle * Add Alert Name to Publishers (#17108) * Add Alert Name to Publishers * Fix Test * Add Bound to Setuptools (#17105) * Minor: fixed testSummaryGraph issue (#17115) * feat: updated multi pipeline ui as per new mock (#17106) * feat: updated multi pipeline ui as per new mock * translation sync * fixed failing unit test * fixed playwright test * fixed viewService click issue * sorted pipeline based on test case length * Added domo federated dataset support (#17061) * fix usernames (#17122) * Doc: Updated Doris & Redshift Docs (#17123) Co-authored-by: Prajwal Pandit <prajwalpandit@Prajwals-MacBook-Air.local> * Fix #12677: Added Synapse Connector - docs and side docs (#17041) * Fix #17098: Fixed case sensitive partition column name in Bigquery (#17104) * Fixed case sensitive partiion col name bigquery * update test * #13876: change placement of comment and close button in task approval workflow (#17044) * change placment of comment and close button in task approval workflow * minor change * playwright test for the close and comment function * supported ref in activityFeedEditor * fix playwright test * added playwright test for data steward * fix the test for the data streward user * fix the close button not showing if task has no suggestions and icon fixes * fix sonar issue * change glossary and add suggestion button to dropdown button * fix the glossary failure due to button change * icon change for add tag and description * fix glossary cypress failure due to button chnages * changes as per comments * MINOR: docs links fix (#17125) * alation link fix * dbt yaml config source link fix * bigquery doc fix * Explore tree feedbacks (#17078) * fix explore design * update switcher icon * show menu when search query exists * fix selection of active service * fix type error * fix tests * fix tests * fix tests * MINOR: Databricks view TableType fix (#17124) * Minor: fixed AUT test (#17128) * Fix #16692: Override Lineage Support for View & Dashboard Lineage (#17064) * #17065: fix the tags not rendering in selector after selection in edit tags task (#17107) * fix the tags not rendering in selector after selection in edit tags taks * added playwright test * minor changes * minor fix * fix the tags not updating in edit and accept tag * fix explore type changes for collate (#17131) * MINOR: changed log level to debug (#17126) * changed log level to debug * fixed type * changed type to optional * Get feed and count data of soft deleted user (#17135) * Doc: Adding OIDC Docs (#17139) Co-authored-by: Prajwal Pandit <prajwalpandit@Prajwals-MacBook-Air.local> * Doc: Updating Profiler Workflow Docs URL (#17140) Co-authored-by: Prajwal Pandit <prajwalpandit@Prajwals-MacBook-Air.local> * fix playwright and cypress (#17138) * Minor: fixed edit modal issue for sql test case (#17132) * Minor: fixed edit modal issue for sql test case * fixed test * Minor: Added whats new content for 1.4.6 release (#17148) * MINOR [GEN-799]: add option to disable manual trigger using scheduleType (#17031) * fix: raise for triggering system app * added scheduleType ScheduledOrManual * minor: remove "service" field from required properties in createAPIEndpoint schema (#17147) * initial commit multi ownership * update glossary and other entities * update owners * fix version pages * fix tests * Update entity_extension to move owner to array (#17200) * fix tests * fix api page errors * fix owner label design * locales * fix owners in elastic search source * fix types * fix tests * fix tests * Updated CustomMetric owner to entityReferenceList. (#17211) * Fix owners field in search mappings * fix search aggregates * fix inherited label * Issue #17012: Multi User/Team Ownership - Fix Tests - Part 9 * Fix QUeries * Fix Mysql Queries * Typo * fix tests * fix tests * fix tests * fix advanced search constants * fix service ingestion tests * fix tests --------- Co-authored-by: mohitdeuex <mohit.y@deuexsolutions.com> Co-authored-by: Onkar Ravgan <onkar.10r@gmail.com> Co-authored-by: Mohit Yadav <105265192+mohityadav766@users.noreply.github.com> Co-authored-by: Ayush Shah <ayush@getcollate.io> Co-authored-by: Shailesh Parmar <shailesh.parmar.webdev@gmail.com> Co-authored-by: k.nakagaki <141020064+nakaken-churadata@users.noreply.github.com> Co-authored-by: Prajwal214 <167504578+Prajwal214@users.noreply.github.com> Co-authored-by: Prajwal Pandit <prajwalpandit@Prajwals-MacBook-Air.local> Co-authored-by: Suman Maharana <sumanmaharana786@gmail.com> Co-authored-by: Ashish Gupta <ashish@getcollate.io> Co-authored-by: harshsoni2024 <64592571+harshsoni2024@users.noreply.github.com> Co-authored-by: Karan Hotchandani <33024356+karanh37@users.noreply.github.com> Co-authored-by: Mayur Singal <39544459+ulixius9@users.noreply.github.com> Co-authored-by: Imri Paran <imri.paran@gmail.com> Co-authored-by: sonika-shah <58761340+sonika-shah@users.noreply.github.com> Co-authored-by: Sachin Chaurasiya <sachinchaurasiyachotey87@gmail.com> Co-authored-by: karanh37 <karanh37@gmail.com> Co-authored-by: Siddhant <86899184+Siddhanttimeline@users.noreply.github.com>
|
Hi @harshach @ayush-shah @TeddyCr , |
|
@nqvuong1998 we decided not to enable multiple team ownership for data assets. Ownership requires taking care of the dataassets, addressing any new requirements and answering to the users of such data asset. Multiple teams means there are many owners without clearly making one team a point of contact. |
|
Hi @harshach, in our use case, we have data asset which belongs to multiple domains, and our data governance framework is designed to support ownership at team level, not just specific user. So given the case, we need to have multiple teams ownership for one data asset. |
|
Hello @harshach, Our organization has the same issue, in some schemas, one table can have the responsibility from different teams as the data belongs to different domains. And to find exactly the ones who are responsible, finding by user is hard (ownership is based on the domains) and collecting all the users into one team is not possible too as the domains are different. Please help us consider if multiple team owner is possible, thanks! |
|
Hello @harshach , are you considering adding multi-team ownership? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ownership of Data Assets
In OpenMetadata, we highly recommend using Team based ownership for any data assets. This is coming from our experience of running data teams small and big. Typical platforms provide an option for users to set ownership to multiple users. Employees tend to leave teams or organizations and the most important part of a data asset is the ownership will become stale
This is one of the important reasons to assign a team based ownership so that the asset ownership is not reflective of a individual(s) rather than a team.
However, many orgs using OpenMetadata felt this is restrictive and requested for multi-owner relationship to Data Assets.
This feature is to enable the multi-user / single-team ownership. In this feature multi-relationship between data asset to users or a single team.
The text was updated successfully, but these errors were encountered: