You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All projects in the 'Projects' overview are sorted by date of creation.
This gets weird as soon as the user imports an old project. The project gets sorted according to the original creation date, instead of the import date. This is especially confusing with a lot of projects in the list.
I suggest using the import date instead of the creation date when importing a project, or give the user a choice to decide for themselves.
Alternatively, sorting options for the Projects overview could be utilized to mitigate this issue.
The text was updated successfully, but these errors were encountered:
We will introduce sorting options for project lists. One of the options will be to sort based on the last updated date of projects, such that active projects are on top of the list and stale projects are below.
Sorting by last update would certainly make this better, but I would prefere to set the creation date = import date.
If I would sort by last update, the order of the projects in our list would change all the time. I can understand that manipulating the creation date feels dirty, but it feels better to me than sorting by last updates.
Alternatively, sorting by "import date/time" would work as well, if projects with not "import date/time" would use the "creation date/time" instead.
All projects in the 'Projects' overview are sorted by date of creation.
This gets weird as soon as the user imports an old project. The project gets sorted according to the original creation date, instead of the import date. This is especially confusing with a lot of projects in the list.
I suggest using the import date instead of the creation date when importing a project, or give the user a choice to decide for themselves.
Alternatively, sorting options for the Projects overview could be utilized to mitigate this issue.
The text was updated successfully, but these errors were encountered: