3e58b6d8d2
* fix(sync): skip file-based conflict dialog for example-only stores (#7985) A fresh file-based client (Dropbox/WebDAV) that seeded onboarding example tasks before its first sync hit a LocalDataConflictError dialog when adopting a populated remote, because hasMeaningfulStateData() counts any task and the isExampleTask marker lives only on the op-log op, not the NgRx Task entity. Derive the pending example-task ids (via the now-shared isExampleTaskCreateOp predicate) and let the file-based store-meaning check ignore them, so an example-only store adopts remote silently — the same smoothing #7976/#7980 gave the SuperSync path (plan §7 "Option 2" for the file-based path). A real task / non-INBOX project / non-system tag / note still reads as meaningful and shows the dialog. hasMeaningfulStateData() gains an optional ignoreTaskIds arg that only narrows the result; omitting it preserves behavior for the #7892 empty-overwrite guard, snapshot/compaction, and first-time-sync callers. Note: the SuperSync upload-pollution residual (Fix C in the #7980 plan) is NOT addressed here — a status-based upload guard is ineffective (hasSyncedOps flips during the pre-upload download) and the correct fix is identity-based cleanup, left as a scoped follow-up. * fix(sync): discard example-task ops on first adoption of populated remote (#7985) The deferred "Fix C" from #7980: a never-synced client that adopts a populated, non-encrypted SuperSync account (seeded by normal upload, so no SYNC_IMPORT fires the incoming-import gate's discard) would upload its 4 onboarding example-task ops onto that remote, propagating throwaway scaffolding to every device. In OperationLogSyncService.uploadPendingOps, when the pre-download-captured isNeverSynced is true AND hasSyncedOps() is now true (this cycle's download just adopted remote ops), reject the pending example-create ops so the upload never sends them. The pre-download capture is what makes this reliable — a live hasSyncedOps() read is useless here because the download flips it mid-cycle (#7980 §10). Stranding safety: discard only from a PRISTINE post-boot batch — example creates plus default GLOBAL_CONFIG writes, nothing else. hasMeaningfulPendingOps() is not sufficient: it ignores Move/Batch (and planner/board/section) ops, which can reference an example task id without being "meaningful". Unlike the incoming- SYNC_IMPORT discard — where SyncImportFilterService drops any concurrent dependent op against the import — this adoption path has no import to filter them, so a surviving reorder Move would strand a dangling reference once its create is rejected. Requiring an all-examples+config batch also preserves "an edited example syncs as real data": any user action (edit, reorder, real task) adds a non-config op and skips the cleanup, so everything uploads together. Scope: stops cross-device propagation (the documented harm). On SuperSync the example tasks remain in this device's local NgRx state (op-based adoption merges rather than replaces); removing them from local state is a separate increment. The file-based path already clears them via snapshot hydration. * test(sync): real-store integration proof for example-task adoption cleanup (#7985) The sync-service unit specs mock opLogStore.hasSyncedOps(), so they only prove the Fix C hook's truth-table — not the load-bearing #7980 §10 claim that the pre-upload download phase persists adopted remote ops with syncedAt (flipping hasSyncedOps() to true) while the local example creates stay unsynced. This integration test exercises the REAL OperationLogStoreService against real IndexedDB: appending a remote-sourced op genuinely flips hasSyncedOps() to true while getUnsynced() still returns the local example creates, the production "pristine post-boot batch" predicate evaluates correctly on real ops, and the real markRejected() removes only the example creates (config survives). Also covers the reorder-Move stranding guard and the empty-server-seeding no-fire case. No docker / SuperSync server needed; complements the (still-recommended) e2e. |
||
|---|---|---|
| .air | ||
| .devcontainer | ||
| .github | ||
| .husky | ||
| .signpath/policies/super-productivity | ||
| .vscode | ||
| android | ||
| build | ||
| docs | ||
| e2e | ||
| electron | ||
| eslint-local-rules | ||
| fastlane | ||
| ios | ||
| nginx | ||
| packages | ||
| scripts | ||
| snap/hooks | ||
| src | ||
| tools | ||
| .browserslistrc | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.example | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .gitpod.yml | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .stylelintrc.mjs | ||
| AGENTS.md | ||
| angular.json | ||
| ARCHITECTURE-DECISIONS.md | ||
| capacitor.config.ts | ||
| CLAUDE.md | ||
| CONTRIBUTING.md | ||
| docker-compose.e2e.fast.yaml | ||
| docker-compose.e2e.yaml | ||
| docker-compose.supersync.yaml | ||
| docker-compose.yaml | ||
| docker-entrypoint.sh | ||
| Dockerfile | ||
| Dockerfile.e2e.dev | ||
| Dockerfile.e2e.dev.fast | ||
| electron-builder.yaml | ||
| eslint.config.js | ||
| funding.json | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| ngsw-config.json | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| tsconfig.base.json | ||
| tsconfig.json | ||
| webdav.yaml | ||
An advanced todo list app with timeboxing & time tracking capabilities that supports importing tasks from your calendar, Jira, GitHub and others
🌐 Open Web App or 💻 Download
💻 Downloads & Install
For all current downloads, package links, and platform-specific notes:
check the wiki
✔️ Features
- Keep organized and focused! Plan and categorize your tasks using sub-tasks, projects and tags and color code them as needed.
- Use timeboxing and track your time. Create time sheets and work summaries in a breeze to easily export them to your company's time tracking system.
- Helps you to establish healthy & productive habits:
- A break reminder reminds you when it's time to step away.
- The anti-procrastination feature helps you gain perspective when you really need to.
- Need some extra focus? A Pomodoro timer is also always at hand.
- Collect personal metrics to see, which of your work routines need adjustments.
- Integrate with Jira, Trello, GitHub, GitLab, Gitea, OpenProject, Linear, ClickUp and Azure DevOps. Auto import tasks assigned to you, plan the details locally, automatically create work logs, and get notified immediately, when something changes.
- Basic CalDAV integration.
- Back up and synchronize your data across multiple devices with Dropbox and WebDAV support
- Attach context information to tasks and projects. Create notes, attach files or create project-level bookmarks for links, files, and even commands.
- Super Productivity respects your privacy and does NOT collect any data and there are no user accounts or registration. You decide where you store your data!
- It's free and open source and always will be.
And much more!
Note
The web version has some limitations: See the Web App vs Desktop comparison for more details.
📖 Documentation and Guides
Getting Started
- Getting started guide (article)
- Video walkthrough (YouTube)
- Eat the frog prioritizing scheme
Starting Point in Wiki:
First steps •
Reference •
How-To
Productivity Tips:
Keyboard Shortcuts •
Short Syntax
Need Help?
Visit the discussions page
See the bottom of the README for more information on the documentation.
Advanced Topics
Here are some other topics covered in the official wiki:
Development:
Run dev server •
Package the app •
Build for Android •
Run with Docker
Data Management:
User Data •
Issue Providers •
Sync Providers
Customization:
Plugins •
Themes
APIs:
Sync Server •
Plugins •
REST
Community
The development of Super Productivity is driven by a wonderful community of users and contributors. Thank you all so much for your support!
👀 Check out our awesome curated list of community-created resources about Super Productivity
♥️ Contributing
If you want to get involved, please check out the CONTRIBUTING.md
There are several ways to help.
-
Spread the word: More users mean more people testing and contributing to the app which in turn means better stability and possibly more and better features. You can vote for Super Productivity on Slant, Product Hunt, Softpedia or on AlternativeTo, you can tweet about it, share it on LinkedIn, reddit or any of your favorite social media platforms. Every little bit helps!
-
Provide a Pull Request: Here is a list of the most popular community requests and here some info on how to run the development build (wiki). Please make sure that you're following the commit message format and to also include the issue number in your commit message, if you're fixing a particular issue (e.g.:
feat: add nice feature #31). -
Answer questions: You know the answer to another user's problem? Share your knowledge!
-
Provide your opinion: Some community suggestions are controversial. Your input might be helpful and if it is just an up- or down-vote.
-
Provide a more refined UI spec for existing feature requests
-
Make a feature or improvement request: Something can be done better? Something essential missing? Let us know!
-
Translations, Icons, etc.: You don't have to be a programmer to help; learn how to contribute translations!
-
Create custom plugins or custom themes
Special Thanks to our Sponsors!!!
Recently support for Super Productivity has been growing! A big thank you to all our sponsors!
(If you are, intend to or have been a sponsor and want to be shown here, please let me know!)
Code Signing
Windows binaries are signed. Free code signing is provided by SignPath.io, certificate by SignPath Foundation.
Documentation: Manual versus Automated
There are two wikis: the official one hosted in by GitHub autonomously generated variant using DeepWiki.com. The manually curated version is a more stable and approachable resource designed to help you understand the app from a more human-focused perspective whereas DeepWiki is optimized for explaining the code itself with little regard for context beyond that.
Official Wiki
It is preferable to maintain local documentation rather than rely on an external service. It also preferable that the documentation is updated in tandem with the code changes as demonstrated in this commit.
Changes to files within ./docs/wiki are linted in CI before being automatically
sync'd to the repository's official Wiki hosted by GitHub.
Migrating to Docusaurus is a long-term goal once the content and structure of the wiki has matured and the remaining "legacy docs" have either been reworked or removed. There are some automations in development to help reduce the difference between the published docs and the state of the code while retaining a human-in-the-loop.
DeepWiki.com
If you have very specific questions about how the code works or why a bug might be producing
a particular message it might be useful to
. It can help "cite your sources" when discussing functionality and code that you don't fully
understand as part of feature requests or bug reports.
This automated reference does come with some significant drawbacks:
- Intent: Describes what code does, not why decisions or tradeoffs were made.
- Staleness: Will *always* lag behind the code.
- Code-Focused: Does not provide guides or conceptual explanations.
- Cost: Potential future cost and higher resource usage than static docs.