Recurring card feature fails to emit necessary events for due date updates and completion status changes, disrupting automations and external integrations

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • Component/s: Card - Card Back
    • None
    • 1
    • Severity 3 - Minor

      Issue Summary

      When a Trello card set to recur is marked as completed, Trello only emits a "complete" event. This lack of additional events causes issues with external services and Trello automations that rely on these events to function properly.

      Steps to Reproduce

      1. Set up a Trello card with a recurring due date.
      1. Mark the card as completed.

      Expected Results

      • Trello should emit an event for the due date being updated to the next recurring date.
      • Trello should emit an event indicating that the card is no longer completed.
      • These events should trigger any relevant automations and be reflected in the activity log.

      Actual Results

      • Trello only emits a "complete" event.
      • Due date updates and changes in completion status are not reflected as separate events.
      • Automations that depend on these events do not trigger.
      • External services and power-ups relying on Trello's card events do not receive necessary updates, affecting their functionality.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Justin Borczuk
            Reporter:
            Nivedhya Vikram1
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: