Developer Experience

Scheduled digests in email digests

PlannedJOJonas Silva

Our support volume would drop noticeably if this shipped. Even shipping it behind a flag would let us validate the approach.

What we would need:

  • CSV export
  • Vote weighting
  • Reaction emoji
  • A public API rate-limit dashboard

14 comments

  • ME
    Mei Ibrahim10 months ago

    Bumping — this is still our top request.

  • AM
    Amara Nakamura8 months ago

    This is on the roadmap for next quarter — following for updates.

  • RA
    Rafael Delgado6 months ago

    We shipped a partial version of this behind a flag. Details soon. Right now this costs us roughly two hours a week.

    • EL
      Elena Ferreira7 months ago

      Closing as fixed in this week's release. Shout if it resurfaces.

  • VI
    Viktor Yilmaz5 months ago

    Is there a workaround in the meantime? Even a manual one would help.

    • DM
      Dmitri ReyesTeam2 months ago

      Strong +1. We ran into exactly this last sprint.

  • SO
    Sofia Haddad4 months ago

    Is there a workaround in the meantime? Even a manual one would help.

  • AM
    Amara Kowalski3 months ago

    Thanks for the detailed repro — that made this much faster to track down.

  • GR
    Grace Reyesabout 2 months ago

    Is there a workaround in the meantime? Even a manual one would help. A rough first version would already be a big improvement.

  • CH
    Chloe Duarteabout 2 months ago

    Closing as fixed in this week's release. Shout if it resurfaces.

  • JO
    Jonas Ibrahimabout 2 months ago

    Could this also cover the API case, or is that separate?

  • MA
    Marcus Duarte29 days ago

    Strong +1. We ran into exactly this last sprint. It would let us retire an internal tool nobody wants to maintain.

  • NA
    Nadia Wu3 days ago

    Strong +1. We ran into exactly this last sprint.

    • CH
      Chloe Okafor7 months ago

      Is there a workaround in the meantime? Even a manual one would help. It would cut a full step out of our triage loop.