you can still fix them by introducing a frontend that uses that structure, no need to limit them from the backend-side
Which creates unnecessary complexity, because when a task turns out more complicated than expected you have to convert a task to a list.
What is the advantage of the separation if you ignore…
Let me lay out my ideal structure and current workarounds, illustrating the superiority of this approach: With everyone in the core team of our company I want to share an uncompletable root…
For me it seems like tasks that do have subtasks are kind of no tasks anymore. They are 'mini-projects'. This raises the question of what the differences is between them and what we call 'lists'…
Is there another communication channel apart from Gitea, Github and Discourse? I am pretty sure I wrote about what I wanted to add here somewhere, but I just can't find it anymore, so I will…
A full n8n integration is really what we want. n8n already has integrations for discourse, zulip, invoiceninja,…
Exactly that is what I meant :)
Furthermore, my colleague just had an issue with his jwt token being invalidated when he clicked on the link, logged in, and closed the popup - it looked like he…
Ah right, I keep making that mistake. Nonetheless, try opening these in a new tab an clicking the x in the popup: https://try.vikunja.io/lists/1/settings/edit https://try.vikunja.io/lists/1/setti…
well, not uncloseable there, but still unexpected: https://try.vikunja.io/list/1/settings/share
Thank you for implementing this! New Release? :)
I guess I'll just tack this on here: Visiting something like /lists/43/settings/share creates an uncloseable popup ^^
I would like to assign the task creator to a task by default if he does not set an assignee initially.
@kolaente this is a priority feature, would you think implementing a proper integration…
Yes that is what I meant, but I mistook something here. Then we should find another way, maybe always showing the "Filters" namespace or, to be less protrusive, having a button "Add saved filter"…
I corrected myself, you were too quick ;)
Furthermore, a (potentially trimmed) list of all available people (including avatars, idk if that is supposed to work already?) should be shown when…
I was thinking of something like in Zulip or Slack, where an abbreviated description is shown next to the channel topic for quick access: ![image](/attachments/4a4962ae-7c0f-4b24-810e-487ca76ec71d…