This moves the identifier and colorpicker below the description field and next to each other.
Additionally this fixes a bug of the identifier, where it was possible to add an identifier with a length greater than 10, that resulted in an error.
in all use cases of `project.title` it's implicit clear that 'project title' is meant. Mentioning 'project' only adds repetitive complexity, since the title of the modals already makes it clear that we are currently editing projects.
This fixes a bug where a query like "labels in lorem || labels in ipsum" would only replace the first occurrence, leading to errors when sending the query string to the api.
Resolves https://github.com/go-vikunja/vikunja/issues/346
This fixes a bug where the task delete modal was not visible on mobile when the task itself was opened in a modal (for example, when opened via the kanban board). This was caused by both the delete modal and the task modal being teleported outside of the app.
Partially resolves https://github.com/go-vikunja/vikunja/issues/383
This improves the UX because it does not allow external users to change their name in Vikunja, since that change would be overridden once they log in again.
Resolves https://github.com/go-vikunja/vikunja/issues/357
This partially reverts a change introduced in ca1384e3c9 which led to a bug where a comment on a task, which was just saved, stayed in the editor. The editor switched to read-only mode after that.
I'm still unsure if we should keep this rule in general, in this specific case I think it makes sense to reverse the logic and enable this api config explicitly
This improves (!) the types of Multiselect — it doesn't fix them
Reviewed-on: https://kolaente.dev/vikunja/vikunja/pulls/2618
Co-authored-by: Dominik Pschenitschni <mail@celement.de>
Co-committed-by: Dominik Pschenitschni <mail@celement.de>
There might be future general improvements like merging the edit and info modal (since they both show the description, but only in one it's editable.
This PR already improves the situation a bit, since you don't have to click on that info button anymore to check __if__ there is a description at all.
This will not fix the current issues yet, but I think it makes sense to start with this to rule this out.
Reviewed-on: https://kolaente.dev/vikunja/vikunja/pulls/2453
Reviewed-by: konrad <k@knt.li>
Co-authored-by: Dominik Pschenitschni <mail@celement.de>
Co-committed-by: Dominik Pschenitschni <mail@celement.de>
Frederick [Bot]
Dominik Pschenitschni
kolaente