Since there doesn't appear to be a way to reproduce this at HEAD, we can't move forward.

Ipsilon support would almost certainly take the form of an auth adapter. Phabricator auth adapters are not restricted to OAuth2: they include LDAP, username/password, OAuth1, and Persona (and T814 has examples that include HTTP Basic / Kerberos-via-HTTP Basic).

Community Resources has some other working examples of auth extensions and Adding New Classes explains how to write them today. But there's no formal support until T5055 / T5447.

We aren't interested in maintaining this since we haven't seen other interest in it, but feel free to add it to Community Resources.

I spent pretty much the whole afternoon yesterday getting "All Day" events working properly without getting a result I was happy with (some of this was untangling date controls, which will probably come upstream eventually).

This isn't a bug. List HTTP and HTTPS if you want to use these protocols.

Ohhh, sorry, I missed that this is a service call thing rather than a redirect/workflow thing.

You could write a CustomField that was hidden and had some static prefilled value for each form, but I think you might have some amount of trouble getting the UX to work well after the task was created (e.g., you can put some "link back to the thing you came from" in the properties, but not easily render a banner at the top of the page with an obvious "continue" button, nor easily detect that the user just created the object and seamlessly redirect).

Some general sorts of thoughts:

My test data is pretty sketchy:

Ah, fair enough. Two options it is, then.

I poked at it a little bit but only got this far:

We can just replace ui.custom-header with two separate options I guess and put deprecation guidance in the old option.

(And no matter what the policy is, this allows attackers to compromise a support account and then strip MFA from a "better" account, upgrading access.)

In the general case, as with the upstream cluster (T7639) I think the quorum thing in T9515 that @eadler mentions is the most promising way forward to reduce MFA support costs. Briefly, it would work like this:

Month view in desktop mode should be flush with box?

Upgrade.

It's intentional that you can not see information about tasks you don't have permission to see.

https://secure.phabricator.com/book/phabricator/article/spaces/

Calendar needs design work after intervening redesigns, but the views have been responsive for some time.

calendar.event.search is still pretty useless/bare-bones (you don't get very much information back), but we can expand that as use cases arise. We don't have specific needs for this yet.

T8267 briefly discussed the idea of automatically selecting an icon if one isn't provided.

Currently, there's no way to create an event without explicitly selecting an icon, so there's no way to really implement this.

This UI needs some cleanup in all browsers after some intervening redesign, but I don't see anything specifically wrong about it in Firefox at HEAD of master.

I'm just going to close this:

We can revisit this later if use cases develop, but we haven't seen any need for it yet.

This is on EditEngine + Modular Transactions now. There are probably still some remaining issues I didn't catch.

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

(Presuming that fixed things until we see evidence otherwise.)

Specifically, this should be resolved by D16242 (July 6).

T11319#185560 has some additional discussion about somewhat-related-ish issues.

It might be reasonable to un-pht() the field names in the short term until this gets solved for real, although it would be nice to see a use case with a legitimate translation rather than Pirate.

This is sort of very vaguely related to T5586, although I don't know if the fix will end up being the same or not.