Improvements tasks

[rubenrouwhof]

Multiple UI/UX Issues in Tasks interface

Description:
1. Navigation Tab Visibility Issue

• Tabs disappear when switching to the Task tab

[Screenshot showing missing tabs]

2. Responsive Design Problems

• Layout breaks at certain viewport sizes
• Content does not adjust properly to screen dimensions
• This is not only a problem on tasks tab, but in the entire application

[Screenshots showing responsive issues]

3. Search and filters

• Incorrect placeholder text in search field and assignee filter. We can skip all placeholders
• Clear button ('x') should only appear when field contains text. Current implementation shows clear button even when field is empty

[Screenshot showing search field issue]

[Screenshot showing placeholders]

4. Order cards
Tickets on the task board should be ordered according to the sequence of measures defined in the Algoritmekader.

5. Breadcrumbs
For the tasks it's ok. (so maybe not the right ticket for it) But other breadcrumbs are not consistent.

[uittenbroekrobbert]

@rubenrouwhof you mentioned:
4. Order cards
Tickets on the task board should be ordered according to the sequence of measures defined in the Algoritmekader.

We can only follow that exact order if we'd copy it or hardcode it. I don't think we can/should to that. What I do now is:

• first sort the tasks on the (first!) lifecycle they are mentioned in
• then sort the tasks on the key-index, like org-1, using a hard-coded list to get the correct order:
  key_index = {"org": 1, "pba": 2, "owp": 3, "dat": 4, "owk": 5, "ver": 6, "imp": 7, "mon": 8, "uit": 9}
  and then on index number, so you'd get org-1, org-2, pba-1, owp-2, etc.

I think this comes most close to the logical order and the order mentioned on the algoritmekader page itself; without having to "copy" any information.

This does assume they keys (org, pba etc) do not change.. and that the index (org-1, org-2) always is in subsequent order.

Is this ok?