marcusolsson / obsidian-projects

Plain text project planning in Obsidian
Apache License 2.0
1.3k stars 44 forks source link

[BUG] Moving notes between kanban boards causes issues with YML across notes. #629

Open cliftonbartholomew opened 11 months ago

cliftonbartholomew commented 11 months ago

What happened?

I am using projects for task managment, each task gets a different note, here is an example of the note template:

image

I use 'area' to filter for a kanban view for each area of my life, work, personal etc. I use 'board' to determine which Kanban board it should be using within that area.

Here is an example of my DEV area: image

The issue: When I move a note from one board to another, some of the notes dissappear from the boards.

Here is an example after moving "Setup bingo site in github" from the "Personal Projects" board to the "Django" board, nothing else was done except drag and drop. Three notes dissappeared from the "Django" board. image

This is what the table view looks like for those 3 tasks that dissappear: image

When I open the note this is what I see: image

Nothing is wrong with the note. Then when I close the note this is what I see (i.e. it is fixed): image

What did you expect to happen?

Notes should not disappear from kanban boards when I am moving things between boards.

How can we reproduce it (as minimally and precisely as possible)?

It only happens sometimes, but it only happens when I move a note from one board to another.

Anything else we need to know?

No response

Plugin version

1.16.3

Obsidian version

1.3.5

OS

Windows

github-actions[bot] commented 7 months ago

This bot triages issues and PRs according to the following rules: - After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interested in reopening

github-actions[bot] commented 5 months ago

This bot triages issues and PRs according to the following rules: - After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interested in reopening