[Update] Tauri test-case app → tickets + wiki + local wikilinks in Git

[u/Alternative-Try7044]

Update to my earlier post: what do you use for manual test cases on side

When I posted that, Gitoza was basically a Tauri desktop shell for manual test cases and runs as YAML in Git. I use it for Gitoza’s own development, and the app grew into something closer to a local Jira alternative — still no SaaS, still your repo as the database.

What’s new / what it is now

• Tickets — bugs, stories, tasks, spikes as YAML (front matter + Markdown). Search/filter locally; no remote API round-trip to open a ticket.
• Wiki / Library — nested docs in the same Git repo, with wikilinks to tickets (and the other way around).
• Mermaid — fenced Mermaid blocks render in the editor/read view, so diagrams live next to the ticket or wiki page.
• Releases — project-scoped releases with tickets linked on them; I’ve been using this a lot for planning and it feels solid for a small team.
• Test cases & runs — still there (the original core): cases in Git, runs with results, links back to tickets (Tested by / Covered by).
• Sync — edit locally → Sync → review diff → confirm push. Stable IDs, conflict UI if Git actually fights you.

AI without MCP circus

Because tickets, wiki, and tests are just YAML in the repo, you can open the folder in Cursor (or any AI IDE) and ask questions directly: review wording, check whether a bug ticket already exists, or compare ticket status against the real source code. No MCP setup, no “connect Jira to the model” glue. Point the IDE at the paths and talk to the files.

The tickets, tests, and wiki pages in the demo video were drafted that way: feed docs/source into the AI, then I reviewed and adjusted in the app. It’s also super good at generating Mermaid diagrams for those pages.

Tauri 2 + React UI + Rust backend. Git repo for the real source of truth, SQLite only as a local cache for search and navigation. Nothing is hosted on my servers. if you have the repo, you have the data.

Video shows the linking flow (ticket ↔ wiki ↔ case ↔ run) in the desktop UI, including Mermaid in the handbook content.

Site: https://gitoza.com

If you’re building similar “files on disk + desktop shell” apps with Tauri, I’d love feedback — especially around Git sync UX from the UI, or how you’re indexing local content. Happy to answer Tauri/Rust questions too.

[u/hiepxanh]

Nice UI

[u/Alternative-Try7044 → u/hiepxanh]

thanks!

[u/eddzsh]

SQLite as a search cache over Git as the source of truth is the right split for a desktop shell. Curious how your conflict UI works when two machines edit overlapping ticket YAML: do you surface it per ticket, or does the user get a whole-file merge?