Another option would be to not mark the task as done when clicking on it but instead move the task one bucket to the right (or left, with a setting). The task detail view would need to at least…
Thought about it, and buckets should indeed equal task status. This would make Kanban much easier and more useful and solve all these issues:
just tested in try - it seems the name matches case-insensitively, but I have to enter the full name - there is no autocompletion: e.g. when selecting a task, clicking assign user and typing "de"…
Case-insensitive matching is a requirement here, assigning people is still quite janky. And finding someone by e-mail-address still does not work, only if I enter the full address which is…
Just to clarify why I am so adamant about this: We discovered Vikunja in our unhappiness with existing project and task management software, as we need a tool with a single source of truth but…
sorry, you are right there, it is too late to work ^^
no I am on 0.19.1 the whole time, and the spinners actually seem to be solved on unstable ;)
Furthermore it would be handy to be able assign users by email and displayname via Quick Add Magic - for the email even without the domain if that is unambiguous (would be perfect for our case, as…
If a task would automatically turn into a list when you add a subtask, we would essentially arrive at the same point ;) otherwise, that would depend on the UX - you would essentially need to…
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…