Allow tasks to be sorted by name

[Ember-Dawn]

Problem

• Projects can be sorted by name.
• Tasks do not appear to have an equivalent name-based sorting option.
• Task lists and dropdowns become difficult to navigate when a project has many tasks.

Requested feature

• Add an option to sort tasks by name.
• Support:
  • Name ascending
  • Name descending

Expected behavior

• Apply the selected order consistently in task lists and task dropdowns.
• Keep the current ordering available as the default or as a separate option.
• Use case-insensitive alphabetical sorting.

[nikbucher]

Hi everyone — I’ve prepared a small implementation for this:

• sorting the task table by name, total time, or progress
• ascending and descending order
• case-insensitive name sorting
• persistence of the selected order
• E2E coverage for the sorting behaviour

I’ve pushed the current implementation to nikbucher/solidtime:feature/tasks-table-sorting.

For now, this only covers the project task table; task dropdowns could be addressed separately. If the approach seems reasonable, I would appreciate a vouch so I can open the PR. I’m happy to adjust the implementation based on your feedback.

[Onatcer]

vouch @nikbucher tasks table sorting

[Onatcer]

took a quick look: looks good and consistent with the other implementations, i might push a refactor in the PR because the pattern is repeated quite a few times now, but that's on me. Feel free to open the PR and we'll take it from there.

[nikbucher]

Thanks for the vouch and the quick review. I’ve opened the PR: #1218

[nikbucher]

took a quick look: looks good and consistent with the other implementations, i might push a refactor in the PR because the pattern is repeated quite a few times now, but that's on me. Feel free to open the PR and we'll take it from there.

@Onatcer Regarding the refactor you mentioned: I had a look as well and put together a possible approach on a separate branch, in case it is useful:

https://github.com/nikbucher/solidtime/tree/refactor/table-sorting-composable

It extracts the shared sorting logic into a composable and migrates the existing sortable tables to use it. I kept it separate so that PR #1218 stays focused and unaffected.

There is also a small, separately committed change that uses the member name as a secondary sort for other member columns.

No worries if you would prefer to handle the refactor differently.