The plugin is sync-friendly because each task is its own file. Conflicts only happen when: Two devices edit the same task before sync resolves. Two devices edit the project file (e.g. reordering tasks) simultaneously. If you do get a conflict, treat the resulting .conflict-N.md files like any other Obsidian sync conflict — diff, merge, delete the stale one.

Troubleshooting and FAQ

Q: My project doesn't show up in the project list

The plugin only looks for projects inside the configured Projects folder. Check: Settings → Project Manager → Projects folder. The path is relative to the vault root. Your project file has pm-project: true in its frontmatter. The file is inside the projects folder, not in a subfolder. If you opened an existing file with pm-project: true already in its frontmatter, run Open current file as project from the command palette to switch from the markdown editor into the project view. See Importing existing notes for how to add that marker and convert a note into a project.

Q: Why is every task a separate file?

Three reasons: Git diffs are clean. One change touches one file. No merge conflicts on a thousand-row task list. Sync is conflict-free. Two devices editing two different tasks edit two different files — nothing to reconcile. You can grep it. Plain markdown means every Unix-style tool works. So does the rest of your Obsidian setup (search, links, graph). The trade-off is more files in your vault. Most projects don't approach the scale where this matters.

Q: I changed status colors but old tasks look wrong

Status colors and labels are read from the current Settings → Statuses every render. If a task still looks wrong, try: Reload the plugin (settings → community plugins → toggle off/on). Confirm the task's status ID matches one in settings. If a status was deleted, the task should already be remapped to the first status — but if you renamed an ID by hand, you'll have orphaned tasks until you fix or re-add it.

Q: How do I delete a project?

Delete the project file and its tasks/ folder (sibling to the project file). The plugin doesn't have a "delete project" button — it would only do the same two-file deletion.

Q: Where are my custom field values stored?

Inside each task's customFields map in its YAML frontmatter, keyed by field ID. See Data format for exact serialization per field type. Deleting a field definition doesn't immediately delete values on existing tasks. The values stay in the YAML until the plugin next rewrites those task files (after any edit). If you re-add a field with the same ID before then, the values reappear.

The most common questions, in one place.

My project doesn’t show up in the project list

The plugin only looks for projects inside the configured Projects folder. Check:

Settings → Project Manager → Projects folder. The path is relative to the vault root.
Your project file has pm-project: true in its frontmatter.
The file is inside the projects folder, not in a subfolder.

If you opened an existing file with pm-project: true already in its frontmatter, run Open current file as project from the command palette to switch from the markdown editor into the project view. See Importing existing notes for how to add that marker and convert a note into a project.

Why is every task a separate file?

Three reasons:

Git diffs are clean. One change touches one file. No merge conflicts on a thousand-row task list.
Sync is conflict-free. Two devices editing two different tasks edit two different files — nothing to reconcile.
You can grep it. Plain markdown means every Unix-style tool works. So does the rest of your Obsidian setup (search, links, graph).

The trade-off is more files in your vault. Most projects don’t approach the scale where this matters.

I changed status colors but old tasks look wrong

Status colors and labels are read from the current Settings → Statuses every render. If a task still looks wrong, try:

Reload the plugin (settings → community plugins → toggle off/on).
Confirm the task’s status ID matches one in settings. If a status was deleted, the task should already be remapped to the first status — but if you renamed an ID by hand, you’ll have orphaned tasks until you fix or re-add it.

Sync conflicts

The plugin is sync-friendly because each task is its own file. Conflicts only happen when:

Two devices edit the same task before sync resolves.
Two devices edit the project file (e.g. reordering tasks) simultaneously.

If you do get a conflict, treat the resulting <file>.conflict-N.md files like any other Obsidian sync conflict — diff, merge, delete the stale one.

How do I back up?

Your vault is the backup target. Anything that backs up your vault (Obsidian Sync, iCloud, Time Machine, restic, git) backs up your project data too. No separate export needed.

Mobile support

Yes — Obsidian’s mobile apps run plugins. The plugin works on iOS and Android. Some interactions (gantt drag, multi-select with shift-click) are easier on desktop.

Can I have multiple projects?

Yes. One project file per outcome. The project list shows all of them; switching is one click.

How do I delete a project?

Delete the project file and its _tasks/ folder (sibling to the project file). The plugin doesn’t have a “delete project” button — it would only do the same two-file deletion.

Where are my custom field values stored?

Inside each task’s customFields map in its YAML frontmatter, keyed by field ID. See Data format for exact serialization per field type.

Deleting a field definition doesn’t immediately delete values on existing tasks. The values stay in the YAML until the plugin next rewrites those task files (after any edit). If you re-add a field with the same ID before then, the values reappear.

How do I report a bug?

File an issue on GitHub. Include:

Your Obsidian version (Help → About).
The plugin version (Settings → Community plugins → Project Manager).
Steps to reproduce.
A minimal sample if possible (a small project file + its task folder).

Open an issue on GitHub — link from the plugin’s GitHub page.

Where to go next

Data format — the schema for hand-editing or scripting.
Vault layout — where files live and how to move them.
Importing existing notes, Archived tasks, Recurring tasks — three workflows not covered in the main guide.