Would a "Countdown Panel" just use a saved "Countdown Query"?
If so, I'd love to be able to query only for Panels where the Countdown ends in <n days or limit the result to n items, so I can only show the most urgent Countdowns when having a lot of upcoming countdowns.

Actually, this will probably take longer to provide guidance for than to implement.

This is extremely old and doesn't have any use case information, which we require for modern feature requests (see Contributing Feature Requests).

We've started using countdowns on our dashboard as well and it's a little distracting/stressful to have that keep updating. It would be cool to have it fully customizable but the compromise plan you posted about would work well for us too.

This is pure scope creep, but I've always found Countdown anticlimactic when it reaches 0. I could imagine having this feature:

I've marked D16287 as fixing this, although it does not fix Countdown (today, only Calendar has the new behavior).

T9854 is also vaguely related, but fairly separate.

There was some unrelated discussion, but I think the original idea was to have a dashboard panel which is only this (panel on its own):

You can panelize a Countdown query now? What's left here? https://secure.phabricator.com/W456

Dashboards need too much work to make this straightforward.

I think this isn't tremendously important for Countdown but should definitely be sorted out before we unbeta Calendar.

It might not be bad to always show timezones in email explicitly to deal with cases related to T3025 better (e.g., you fly to the east coast for a conference, get prompted to reconcile your timezone after T3025, and it may not be obvious that this also affects mail you receive until you return and re-reconicle back to PST).

With metamta.one-mail-per-recipient on, we can adjust this to the viewer's preferences.

That's why I'm requesting that, you can already CC yourself, but not others :-/

That is, it already supports subscribers, the field just never got built in the UI.

We probably will build this sooner or later since it's free when Countdown eventually swaps to EditEngine.

Calendar is the expected application to use for this need, not Countdown. We don't have any plans to implement new features into Countdown since they'd directly overlap with features already existing in Calendar. I doubt this is something the upstream will ever build, but I'll leave it open in case someone want to contribute a patch.

Calendar doesn't have the advantage of a countdown, and it is an advantage to create a calendar and a countdown event. I don't think a CC bar makes Countdown really more complex, it would only look a bit more like some other appilcations.

I'm not sure how making Countdown more complex solves anything. It seems your root problem is already solved by Calendar?

In some cases countdowns are more useful, because

• It is very simple
  • You got only the start date, for exmaple for a product release
  • You got not a lot of data, e.g. invitees, duration, end date, so you just have to set date and description, and you can use it

That's why in some situation countdown is better. This doesn't means, that I don't use calendar, but for some things countdown is better, because it is simple, and fast.

My problem at the moment, is that I'm using countdown for events.

test

can confirm...

I see. Thanks.

Repeating events are available in Calendar with much more integrations.

Looks resolved, anything else to do?

Ran into this too. It really should give the possibility to order countdowns by the end date in the feeds.