Due date for cards?

[mbajur]

Hey! First of all - thank you for opensourcing this amazing project.

I was wondering if Fizzy team is by any chance considering adding card due dates at some point in the future? This one is the only feature missing to make me use Fizzy for project planning with my customer instead of Trello and it would be great to know if such thing is even planned/considered :)

[attila-kocsis]

This, and adding a list view of tasks with just the title and due date.

[brian]

It's possible, but no immediate plans. We actually had dates on cards at one point, but dropped them because they didn't get used. We have a high bar for what makes it into v1.

The dates also didn't really due anything — we knew we'd need to add a way to see upcoming dates, maybe special handling for overdue cards, reminders, etc...

Totally get that they're key to how many companies work, so it's not out of the question. Thanks for the question and kind words @mbajur!

[JayGhiya]

time bound tasks induce positive pressure and also give a idea for how long certain features would take. Launching products in any domain is based on time to value (ttv) . if time is not measured it becomes very hard. so it also is not about just due date even start dates are helpful as these things need to be done little while from now

[seththoburn-cc]

I'm also really enjoying Fizzy! Due dates would be wonderful, along with what you mentioned, a way to view cards on a calendar and perhaps some handling around overdue cards.

[mderazon]

@brian perhaps instead of adding specific predefined fields like due dates, a more flexible approach would be a card metadata API - a simple key-value store attached to each card, similar to Stripe's metadata.

The idea: allow arbitrary string key-value pairs to be set on a card via the API:

PATCH /:account/cards/:number
{
  "metadata": {
    "due_date": "2026-04-15",
    "priority": "high",
    "customer_id": "acme-corp",
    "estimated_hours": "8"
  }
}

This wouldn't require any UI changes - metadata fields don't need to surface in the card UI at all. The value comes from:

• Filtering via API/CLI: GET /cards?metadata[due_date]=2026-04-15
• Building on top of Fizzy: external tools, scripts, and automations can attach and query any structured data they need without Fizzy having to know about it
• Flexibility over rigidity: instead of Basecamp deciding which fields matter (due date, priority, etc.), each team defines their own schema

Implementation-wise this is a small change - a metadata jsonb column on cards, permitted in the controller, included in the JSON serializer, and optionally filterable. The schema stays clean while the API becomes significantly more powerful for programmatic use cases.

[brian]

That's a simple approach, appreciate it. I don't see us going down this path without metadata support in the UI as well and we don't have appetite for it right now. Great candidate for a local/self-hosted version, though.

[SamuelAierizer]

It would be great to have due dates. And because very probably we already have SMTP configured an option to subscribe to email notifications to reminders would also be very useful imo.