-
Notifications
You must be signed in to change notification settings - Fork 0
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
Define order of task groups in new task-group page #581
Comments
= If we have 10 versions of fractal-tasks-core installed, we still just see it once, right? Re ordering: If we think of this as a table, can we make it user reordable by different columns? e.g. reorder by I think we need to start with a basic version of this and iterate a bit. Or we mock desired outcomes. For the task list, I'm not as picky as for the task addition in workflows, so fine if we slowly iterate on this |
High-level: Let's start with a basic single list, ordered by package name. And then iterate further. Maybe we want different tables, but could also imagine reorderable tables, searchable tables or something else |
That's correct: they should all appear as a single collapsed item.
Our first plan is the following. Let's say that we have collected several versions of two packages, and then we also have added a single task and performed a custom task collection.
The different items expose different UI
If the nested task-list table is too heavy, we can iterate on this and possibly move to a modal - but that it is not our first option (although it would be simpler to implement). |
Ordering by pkg_name is well defined. Ordering by timestamp_created: how would it work? Each collapsed item may include several versions, created at different times. Do we only consider the timestamp of the latest-created version? |
Sounds like a great first thing to implement! |
The first structure of this new page (that replaces the current "Tasks" page) is defined in #579.
A specific question concerns the organization of the different task groups (which will be already aggregated in terms of their pkg_name).
The data we start from is a list of task groups which (among others) have these attributes:
user_id
) and "other people task groups (the ones to which I have access due their usergroup).pkg_name
.group_name
, and thenpkg_name
.Note: this issue does not concern disambiguation rules for when the same task exists in multiple copies (one created by me, one created by userX and assigned to group All, ...). For the moment we are showing the whole list of task groups, without disambiguation logic.
The text was updated successfully, but these errors were encountered: