fe3b97524a
* feat(planner): add Repeat button to schedule dialog
Surface recurrence directly from the schedule dialog via a "Repeat"
button that opens the existing repeat-config dialog, so setting a task
to recur no longer requires the separate detail-panel row.
- Button mirrors the repeat dialog's own start-date button styling and
shows the live recurrence label ("Daily", "Mon–Fri", ...) or
"Does not repeat", with an edit/chevron affordance.
- Gated to top-level, non-issue tasks (matching the panel's Repeat row)
and hidden in isSelectDueOnly mode to avoid a circular picker.
- Recurrence start is seeded from the date currently selected in the
dialog, falling back to the task's due day / creation date.
- Label reads the repeat cfg via the store selector (not the service)
to keep the dialog's dependency surface minimal.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0176AgeeX2Tzv3KjmwZ7zWXC
* feat(tasks): merge recurring into the schedule item in task detail panel
Fold the standalone "Repeat" row into the schedule/due item so a task's
timing lives in one place. The schedule item now also shows the
recurrence label (e.g. "Daily") beside the due date, and recurrence is
edited via the Repeat button now hosted in the schedule dialog.
- Remove the separate Repeat row and the now-unused editTaskRepeatCfg()
opener; recurrence editing goes through the schedule dialog.
- Show a repeat chip in the schedule item's value when repeatCfgId is
set, and treat repeatCfgId as "has a value" for the add/edit icon.
- showScheduleIcon() falls back to 'repeat' for a recurring task with no
due date instead of the misleading 'alarm'.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0176AgeeX2Tzv3KjmwZ7zWXC
* style(datetime-picker): tighten spacing in the schedule picker
The date/time picker left noticeable dead space between the calendar and
the time input, and between the stacked time and reminder inputs.
- Shrink the fixed calendar height 400px -> 360px. A 6-row month (the
structural max) needs ~353px, so the old value left ~47px of empty
space below the grid; 360px fits every month with no clipping.
- Drop the calendar-to-inputs top margin and the reserved Material
form-field subscript row (these fields never show hints and always
carry a valid value), so the time and reminder inputs sit closer.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0176AgeeX2Tzv3KjmwZ7zWXC
* style(tasks): stack recurrence under the due date in the schedule item
When a task was both planned and recurring, the schedule item crammed
the date ("Today") and the recurrence ("Every day") side by side in the
narrow value column, squeezing both and truncating the recurrence label.
Present them as a hierarchy instead: the due date is the primary value
and the recurrence is a muted secondary line stacked beneath it. Reads
clearly, avoids truncation, and gives the row label room to breathe.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0176AgeeX2Tzv3KjmwZ7zWXC
* style(datetime-picker): unify vertical spacing below the inputs
The form-ctrl-wrapper carried a bottom margin on top of each field's own
~16px trailing space, so whatever followed the inputs sat 32px away —
twice the gap between the stacked fields themselves. In the schedule
dialog this left the Repeat button visibly detached; the deadline dialog
had the same doubled gap before its actions.
Drop the redundant bottom margin so the inputs, the Repeat button, and
the dialog actions all share one consistent 16px rhythm.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0176AgeeX2Tzv3KjmwZ7zWXC
* fix(planner): harden schedule-dialog recurrence + polish merged item
Review follow-ups across the recurring/planned consolidation:
- Fix a duplicate-cfg bug: openRepeatDialog seeded the repeat dialog from
the frozen MAT_DIALOG_DATA snapshot, so re-opening after a repeat was
just created routed to "create" again and orphaned the first cfg. Seed
from the live store task instead, so the second open edits.
- Drop the ineffective "seed recurrence start from the selected date"
logic and its misleading comment: the repeat dialog derives the start
from the task's due date; targetDate only drives the skip-instance UI.
Behaviour now matches task.component's opener exactly.
- Break the schedule-dialog <-> repeat-dialog module cycle with a lazy
import, matching task.component / add-task-bar.
- Panel: give the recurrence line a screen-reader "Repeat:" prefix
(cdk-visually-hidden) and let long labels ellipsis within the flex row.
- Align terminology: ADDITIONAL_INFO.REPEAT "Recur" -> "Repeat" (the
add-task-bar and schedule dialog already say "Repeat").
- Use --bar-height token instead of a raw 48px in .repeat-btn.
- Add coverage: canRepeat gating (incl. isSelectDueOnly), the live-task
seeding regression, and showScheduleIcon's new 'repeat' branch.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0176AgeeX2Tzv3KjmwZ7zWXC
* test(recurring): follow schedule dialog repeat flow
Update shared Playwright helpers and direct callers after the standalone Repeat row moved into the schedule dialog.
* style(planner): remove one-off Material overrides
Use stock button presentation and the supported dynamic subscript API instead of local Material internals.
* style(planner): distinguish configured repeat values
Emphasize active recurrence while keeping the non-repeating state visibly muted.
* fix(recurring): avoid warning for newly added config
Require removal confirmation only when recurrence already existed before the enclosing schedule dialog opened.
* fix(recurring): preserve schedule context in repeat dialog
Seed new repeat configs from the current Schedule selection and suppress removal confirmation only for the exact config created in that dialog session.
Update the repeating-task guide and add regression coverage for date and config provenance.
* test(recurring): target combined schedule value
---------
Co-authored-by: Claude <noreply@anthropic.com>
|
||
|---|---|---|
| .agents/skills/commit-messages | ||
| .air | ||
| .codex | ||
| .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 and the 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.