Current Issues

Open Heiss opened this issue 1 year ago • 6 comments

date 1.8. v1.0.12

[ ] again labels bugged -.- multiple labels created sometimes.
- [ ] because of a bug, tasks could be have the same labeltitle duplicated, so my current approach does not fix this
[x] add a dedup labels command, so if it goes south next time, it can be fixed manually
[ ] insufficient permissions not communicated to users
- permissions are not checked previously, so if there are missing permissions, it is in console... see #6
- preparations made in 31eee7f066f2729f35c0c49f2e952e99102df26a
- todos added for further implementations
[ ] preparation for multi-user usage
- currently there is no date, where last sync was happened
- with such a field, we can find out, if a task was newly created or removed. see #12
- with the cache there is also a better way to handle changes, see #14
[x] Command Reset instance cannot handle tasks without an id, so it fails, if there are mixed tasks, which are (not) synced. f6f28843b283504025c01c4c3bb4f83e2b06d448
[x] there is a timerace between changes and dataview indexing, which results in outdated results in request dbf750745983864aa0daf7cf3b7f263917702a08

[x] skip tasks, if the updated value is the same, otherwise unneeded update requests are done - was already there
[x] removing tasks in vikunja, if they are not present in obsidian does not work e552cc1ffafd81d1ce8a6881a85d0c12f4f15384
- remove the correspondig setting, because with the cache we now know what task was deleted since last time, because a task is only in cache, if it got a taskId, so we can keep track
[x] plugin does not get all tasks over the serverside limit 4cf8876629a8fd067ce2dc0216d027c7be5feda9
- because of performance and request limits, it needs requests in batches.
[x] at first sync, it creates some tasks multiple times in vault, which is clutter and maybe something is broken
- maybe dataview returns the same task multiple times, if it has subpoints or subtasks?
[x] add command to reindex the cache. a918fb3f561b2b07b29182ed2b81e7ff6bef0553
- This will use the last modified date as updated field. But this is better then broken cache.

[x] buckets in vikunja are not respected, so if syncing, it overwrites the current bucket, mostly back to default one
- so kanban etc. cannot be used
- sync should overwrite task title, status, etc. but not bucket.
[x] add a link to obsidian file in task description
- there is an option now to enable it, but it is not currently supported, see https://github.com/go-vikunja/vikunja/issues/306

[x] update on cursor movement does not work, if there is no id in the line found
- it should create a new task and work exactly the same as sync, but for only one task
[ ] sync of a preexisting vault does take some minutes
- would be better with an option only to sync not completed tasks to vikunja instead of all

[ ] add a notification, if cors configuration is wrong at serverside, see https://github.com/Heiss/obsidian-vikunja-plugin/issues/16#issuecomment-2295998460
[x] if bucket got changed on vikunja, but there is a status change in vault, the bucket info gets lost
[ ] add setup guide in readme and maybe a modal for first setup https://github.com/Heiss/obsidian-vikunja-plugin/issues/17#issue-2478274945

Aug 01 '24 20:08 Heiss