Advanced Task Options
Beyond the basics of "type a title, click Add", ClientCove tasks have a few power-user mechanics worth knowing — recurrences with non-obvious carry-over rules, and a calendar view with specific behaviors around drag-to-reschedule and out-of-week tasks.
Recurring Tasks
A recurring task auto-creates its next occurrence the moment you mark the current one complete. There's no separate "schedule" — the recurrence is a property of the task itself.
Use cases:
- Weekly client check-in emails
- Monthly invoicing
- Daily stand-up notes
- Quarterly business review prep
How Recurrence Triggers
The next occurrence is created at the moment you tick the completion checkbox:
- You mark the task complete
- ClientCove looks at
task_recurrence— if it's anything other thannone, it callscreate_recurring_task() - A new task post is created with the title and most fields copied
- The new task's due date is the original's due date plus the recurrence interval
- The new task lands at the top of the To Do list (
task_order = 0)
You don't see a confirmation — the new task just appears in your To Do filter immediately.
Recurrence Intervals
The dropdown in the inline task editor offers seven options:
| Option | Status | Behavior |
|---|---|---|
| None | Working | No new occurrence is created |
| Daily | Working | Next due date = current + 1 day |
| Weekly | Working | Next due date = current + 1 week |
| Bi-weekly | Working | Next due date = current + 2 weeks |
| Monthly | Working | Next due date = current + 1 month |
| Quarterly | Not yet implemented | See Known Limitations |
| Annual | Not yet implemented | See Known Limitations |
For now, stick to Daily, Weekly, Bi-weekly, or Monthly if you need automatic recurrence to actually advance the date.
What Carries to the Next Occurrence
When a new occurrence is created, these fields are copied from the completed task:
| Field | Carries? | Notes |
|---|---|---|
| Title | Yes | Same post_title |
| Author | Yes | Same post_author (the task stays with you) |
| Notes | Yes | task_notes |
| Priority | Yes | Whatever you set last |
| Client | Yes | task_client_id |
| Recurrence | Yes | The series continues |
| Due date | Yes (advanced) | Original date + interval |
| Related entity | Yes | task_entity_type + task_entity_id |
| Task list | Yes | task_list_id |
| Completed | Reset | Always false on new occurrence |
| Time spent | Reset | Always 0 on new occurrence |
| Date completed | Reset | Empty on new occurrence |
These fields do not carry over and have to be re-applied if you want them on the next occurrence:
- Tags (
task_tagspost meta) — lost on each occurrence - Source link (
task_related) — the new task is no longer linked to the original ticket / project / message - Created-from origin (
task_created_from) — the new task shows asmanual - Project card sync (
task_sync_with_card) — disabled on the new occurrence - Notes from the project card — if the original card description changes, the recurring task won't update
If you rely on tags for filtering, the loss of tags on each recurrence is the biggest gotcha. For now, manually re-tag each new occurrence after it's created, or use Bulk Edit to apply tags to a week's worth of recurrences at once.
Known Limitations
Quarterly and Annual recurrences don't advance the date
The recurrence dropdown shows Quarterly and Annual options, but the backend handler (create_recurring_task() in task-functions.php) only has cases for daily, weekly, biweekly, and monthly.
What actually happens if you pick Quarterly or Annual and complete the task:
- A new task is created
- Its due date is the same as the original (the date-advance switch falls through with no matching case)
- The recurrence value is preserved, so completing that task creates yet another with the same due date
Effectively, Quarterly and Annual loop forever on the same date until you manually change the recurrence to None.
Workaround until the backend supports them:
- For quarterly cadence, use a recurring monthly task and complete only every third occurrence (delete the in-between ones)
- For annual cadence, use Bi-weekly and rely on a calendar reminder elsewhere
- Or: leave the task on Monthly, and adjust the due date manually to the next quarter/year on each completion
Recurring tasks created from project cards lose the card link
When a task auto-created from a project card has a recurrence set, the next occurrence is no longer linked to the card (task_related_card_id is not copied). The original task keeps its link; the new occurrence is a fresh standalone task.
This is intentional in spirit — a project card is usually a one-shot deliverable, not a recurring series — but if you want a recurring pattern tied to a project, set the recurrence on a manual task and reference the project via the Reference tab instead.
Recurring Tasks Without a Due Date
If a recurring task has no due date when you complete it, the new occurrence is created with no due date either — there's no anchor date to advance.
This means:
- The recurrence keeps creating tasks indefinitely each time you complete one
- None of them ever appear in the Today filter or the Calendar view (no due date)
- They just stack up in the To Do filter
If you want a recurring task that doesn't have specific dates but should still be reminded weekly, set the due date the first time, then accept that the auto-advance keeps moving forward.
Stopping a Recurring Series
To end a recurring series:
- Open the active task (the most recent occurrence)
- Click the Recurrence dropdown
- Choose None
- Complete the task as normal — no new occurrence will be created
If you want to delete the entire history of past occurrences, each completed/archived occurrence is its own post — use the Bulk Edit mode in the Completed or Archived filter to delete them in bulk.
Calendar Week View Deep Dive
The Calendar view (toggle from the view-mode buttons in the toolbar) shows tasks bucketed by day for the current week.
Week boundaries
The week starts on Sunday and ends on Saturday. Day columns are labeled SUN, MON, TUE, WED, THU, FRI, SAT, with an eighth NO DATE column on the right for unscheduled tasks.
Today's column has a highlighted header so it's easy to spot.
Week navigation
The header above the grid has three controls:
- ‹ previous week (subtracts 7 days)
- Today — jumps to the week containing today
- › next week (adds 7 days)
The center label shows the week range, e.g. April 28 – May 4, 2026 (or month-spanning: April 28 – May 4, 2026 — month names switch when the week crosses a boundary).
Per-day actions
Each day column shows:
- A header with day name + day number
- A list of tasks due that day (compact rows with a checkbox + title)
- A + Add task link at the bottom — click to create a new task pre-dated to that day
Click any task title in the calendar to open the task in the underlying List view's expanded editor (the calendar view itself doesn't have an inline editor — use the date for visual planning, switch to List for detail edits).
Drag-to-Reschedule
Drag any task between day columns to change its due date.
- Day → Day: sets the due date to the destination day
- Day → NO DATE: clears the due date entirely
- NO DATE → Day: schedules the task to that day
The update is optimistic — the task moves visually immediately while the API call runs in the background. If the API call fails, the task snaps back to its original column and an error is logged to the console.
Completed tasks can be dragged too (the strikethrough styling stays).
Tasks Outside the Visible Week
A critical thing to know: the calendar view only shows tasks whose due date falls within the currently displayed week (or in the NO DATE column).
If you have a task due in three weeks, it's invisible until you click forward to that week. Likewise, tasks due last week disappear when you advance.
To see "everything coming up":
- Switch to List view and use the Date filter (Today / This Week / Overdue)
- Or use the Today filter tab for just today's items
The calendar is best for week-by-week planning, not as a queue of upcoming work.
Bulk edit and the calendar
Switching to Calendar view automatically exits Bulk Edit mode and clears the current selection. If you need to operate on many tasks at once, switch back to List view first.