[bug] in custom status when moving tasks to column the tasj doesn't stick

[mptpro]

For example,

1. Let's say I have a custom status column "A".
2. I have a task in the "no status" column and drag it to the "A" column.
3. The task appears under column "A" for about 2 seconds but then dissapears and moves back to the "no status" column.
4. when inspecting the task the frontmatter does correct show "status: A"

If you need screenshot or logs, let me know.

version linux 2.31

Ps excellent software!

[adibhanna]

Fixed in commit 70301ce on the v2.32.0 branch.

The server task scanner now returns the same custom fields / status data as the desktop parser for whole-note tasks, and it also mirrors inline @key:value parsing. That keeps a card in its new custom-status column after the watcher rescan or a manual refresh instead of sending it back to No status.

Verified with regression coverage for the reported file-task case and inline custom fields, the full server test suite, the web production build, shared-domain typechecking, go vet ./..., and a live server-backed Kanban demo.

Thanks for the clear report!