kobotoolbox / kpi / 12163184395

82%

master: 76%

push

github

feat(organizations): add `owner_label` field to `AssetSerializer` TASK-1181 (#5312)

### 📣 Summary
Added `owner_label` field to the Asset API to clarify ownership
information, dynamically reflecting either the owner's username or the
organization's name.



### 📖 Description
The `owner_label` field in the Asset API now dynamically displays:

- The username of the asset owner if the organization is not a
multi-member organization (MMO).
- The name of the organization if the organization is a multi-member
organization (MMO) and the user is the organization owner.
This enhancement improves clarity by providing contextual ownership
details directly in the API response.



### 👷 Description for instance maintainers
This update introduces a new owner_label field in the Asset serializer:

- The field logic dynamically evaluates the organization's multi-member
status (is_mmo) and ownership (is_owner).
- Efficient database queries and optimizations ensure minimal impact on
performance.



### 👀 Preview steps
1. ℹ️ Have an account and at least one asset in a project.
2. Ensure the asset belongs to a user who is also an organization owner.
3. 🟢 Verify that the API response for the asset includes owner_label
reflecting the username of the owner.
4. Change the organization's status to a multi-member organization
(enable is_mmo).
5. 🟢 Verify that the owner_label in the API response now reflects the
organization's name.
6. Transfer ownership of the organization to a different user.
7. 🟢 Verify that the owner_label reverts to the original owner's
username.


### 💭 Notes
- Testing: Unit tests were added to validate the owner_label behavior
under various conditions, including ownership changes and multi-member
organization scenarios.
- Performance: The implementation minimizes additional queries by
prefetching related data and leveraging efficient annotations.
- Scalability: The logic is designed to handle a large number... (continued)

5740 of 9222 branches covered (62.24%)

16 of 16 new or added lines in 3 files covered. (100.0%)

21888 of 27249 relevant lines covered (80.33%)

0.8 hits per line