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

Admin page for task groups #619

Closed
tcompa opened this issue Oct 29, 2024 · 1 comment · Fixed by #620
Closed

Admin page for task groups #619

tcompa opened this issue Oct 29, 2024 · 1 comment · Fixed by #620

Comments

@tcompa
Copy link
Collaborator

tcompa commented Oct 29, 2024

In the admin area, I propose that we build a new task-groups page rather than just updating the tasks one. We can later decide whether it's worth merging them together or keeping them separate.

The new page would have a structure similar to the current standard-user task list (in v2/tasks), with a few differences:

  1. The relevant endpoint would be GET /admin/v2/task-group/
  2. We should have additional UI for optionally adding query parameters to this API call:
  3. We should not apply disambiguation to the response data.
  4. The previous point means that we'll need a different aggregation logic, because there will be multiple copies of the same task group. We can start with "no aggregation at all" (that is, one item per task group), and then iterate on this.
  5. We should display additional ownership information, namely which user owns the task-group (as defined in the user_id foreign-key).
  6. We should display the same action buttons as in the standard user page (info/edit/delete), but in order to actually use the edit/delete we first need Let superuser edit/delete taskgroups fractal-server#1974.

I would start with this skeleton, and then we can decide whether we want to add pagination or fancier aggregation or other improvements - if needed.

@zonia3000
Copy link
Collaborator

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

2 participants