**Version information:**
Frontend Version: 0.19.1+116-f083f181e2
API Version: v0.19.2+5-d8f387f796
Browser and OS Version: All
**Steps to reproduce:**
<!--
Add clear steps to reproduce the bug. Provide screenshots where applicable.
-->
1. Create a task that has child tasks and look at them in the list view:

2. 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:**
* [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)
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 :)
Version information:
Frontend Version: 0.19.1+116-f083f181e2
API Version: v0.19.2+5-d8f387f796
Browser and OS Version: All
Steps to reproduce:
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:
Do you have a good idea on what that would look like?
Not currently. No What I didn't check how it currently looks like if there is a parent from another list.
I think the way to go is #363 to solve this.
Heartly agree !
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 :)