A Jira-style task tracker over a flat folder of markdown files.
A Jira-style task tracker for Obsidian. Tasks are plain markdown files in a flat folder; filtering, editing and comments happen in a two-pane GUI.
---
id: TASK-42
title: Fix login redirect
status: In Progress
assignee: Ahmed
due: 2026-09-28
created: 2026-09-21T08:45:00
updated: 2026-09-21T09:10:00
---
## Description
The redirect loops when the session cookie is stale.
## Comments
### Ahmed — 2026-09-21T09:10:00
Reproduced on staging.
Anything else you write in the file is left alone by the plugin.
Section boundaries (## Description, ## Comments, ...) are found by
scanning for the next top-level ## heading. If you type a ## heading
of your own inside a description or comment, the plugin demotes it to ###
when saving so it can't be mistaken for a section boundary — your heading
and its text are kept, just one level down.
TASK produces TASK-1, TASK-2, …Deleting a field hides it but leaves the data in your files. Use Clean up orphaned frontmatter keys when you want it gone for good.
npm install
cp .env.example .env # set VAULT_PATH to the vault you test against
npm run dev # watch build, copies into the vault on each rebuild
npm test # unit tests
npm run typecheck
docs/manual-test.md is the checklist for the parts unit tests can't reach.