Parent task indicator can easily be confused for namespace prefix #2454

New Issue

dpschen · 2022-10-01T11:07:21Z

dpschen commented

2022-10-01 11:07:21 +00:00

Version information:

Frontend Version: 0.19.1+116-f083f181e2
API Version: v0.19.2+5-d8f387f796
Browser and OS Version: All

Steps to reproduce:

Create a task that has child tasks and look at them in the list view:
Look at tasks that belong to different lists, e.g. in the Overview

Expected behavior:

Both prefixes are clearly distinguishable.

Actual behavior:

They can be confused for each other.
The only visual cue that one is a child task is the > suffix.

Checklist:

I have provided all required information
I am using the latest release or the latest unstable build
I was able to reproduce the bug on try

**Version information:** Frontend Version: 0.19.1+116-f083f181e2 API Version: v0.19.2+5-d8f387f796 Browser and OS Version: All **Steps to reproduce:**  1. Create a task that has child tasks and look at them in the list view: ![image](/attachments/6055c81b-0590-4396-b6b3-cab5e365f5c0) 2. Look at tasks that belong to different lists, e.g. in the Overview ![image](/attachments/6e41692e-d60e-4899-821e-2eae5e021661) **Expected behavior:** Both prefixes are clearly distinguishable. **Actual behavior:** They can be confused for each other. The only visual cue that one is a child task is the `>` suffix. **Checklist:** * [x] I have provided all required information * [x] I am using the latest release or the latest unstable build * [x] I was able to reproduce the bug on [try](https://try.vikunja.io)

image.png

37 KiB

image.png

12 KiB

dpschen added the

changes requested

label 2022-10-01 11:07:31 +00:00

konrad added

kind/feature

and removed

changes requested

labels 2022-10-01 12:03:52 +00:00

konrad commented

2022-10-01 12:04:09 +00:00

Do you have a good idea on what that would look like?

dpschen commented

2022-10-01 12:27:16 +00:00

Poster

Not currently. No What I didn't check how it currently looks like if there is a parent from another list.

xeruf commented

2022-10-11 22:08:14 +00:00

I think the way to go is #363 to solve this.

I think the way to go is https://kolaente.dev/vikunja/frontend/issues/363 to solve this.

👍 1

bolgrov commented

2022-11-04 11:12:35 +00:00

I think the way to go is #363 to solve this.

Heartly agree !

> I think the way to go is https://kolaente.dev/vikunja/frontend/issues/363 to solve this. Heartly agree !

dpschen commented

2022-11-04 13:00:46 +00:00

Poster

I think the way to go is #363 to solve this.

While I agree that there needs to be a better overall solution for this, we might want to have an in-between solution for this, because we need a solid plan and archtecture if we want to implement such a change. See what I wrote in #363 for more details.

So see this more as a quick-fix until we get to #363 :)

> I think the way to go is https://kolaente.dev/vikunja/frontend/issues/363 to solve this. While I agree that there needs to be a better overall solution for this, we might want to have an in-between solution for this, because we need a solid plan and archtecture if we want to implement such a change. See [what I wrote in #363](https://kolaente.dev/vikunja/frontend/issues/363#issuecomment-36113) for more details. So see this more as a quick-fix until we get to #363 :)

Sign in to join this conversation.