This is particularly problematic in the UI when you need to revert the first change to a task since creation - there doesn't appear to be any way to find the initial assignee of https://phabricator.wikimedia.org/T129128#2105237 for example

I don't think in our wildest dreams we ever expected that volume on custom forms. Unfortunately we're very unlikely to add a setting/preference for points, given we don't have any settings for these forms and we're fairly allergic to settings overall (T8227). I can't think of any other path forward here, maybe you can script custom forms themselves? I think EditEngine itself is available over Conduit?

43 — we've so far encouraged project owners to use these in order to get the information they need on new tasks / bug reports / etc.

How many create forms do you have?

any future forms will fall back on Points = 0.

Yes that is what I found.
I can't confirm it was ever different :)

Actually I think I understand what you're saying, but I'm not positive it ever worked like you expect, but maybe it did.

I can't reproduce this locally nor on this install. What steps can I take to reproduce the issue you are seeing?

Since the same root problem you described was solved with adding the query icon and link, I'm going to close this out. Overall having this in it's own element lends to better discoverability, and solves the right problem vs. just hiding it in the header. Adding to both is possible, but falls under "Design Feedback" which we don't take as tasks on (see T10208).

It's a tab panel, not a query panel.

The "Issue Events API" appears to provide the remaining events in a different format with different rules. It does not provide any duplicate events, so, e.g., one API retrieves issues being created and commented on while a different API retrieves labels, milestones, etc., except that both report opens and closes, I think. Anyway, seems mostly workable.

Alright, so here's the first real issue. Here's what I did on GitHub:

Oh, yes. I wonder why I did not notice this. Why doesn't the panel "Recent Tasks" on Dashboard 8 have a ?

i ran into the same problem

Ok seems reasonnable :) Thanks for the answer !

When managing our task-load the first things I scope out to get "the lay of the land" for a task are:

• Author
• Assignee
• Status
• Tags
• Created Date

Regarding the space tags take up on workboard cards - would having tags without names (just icon/color) be hiding too much?

Thanks for all the examples - definitely makes sense that these behaviors are a bit of a different class than ones that actually examine file content.

is there a way to add subscribers via lint rules?

I suppose the rules I am writing are fairly lint-like; part of this
reflects the sorry state of our lint infrastructure, though it is probably
a bit more flexible than herald. Having said that, sometimes I do want to
have rules that subscribe me to various diffs, before I figure out how to
automate my own advice; is there a way to add subscribers via lint rules?

Hi guys,
Same issue here!

Primarily, I'm just hesitant to make changes where you upgrade and previously-private stuff becomes public, since I think that's a terrifying behavior in the general case and maybe even worse than destroying data.

To provide a little context, I suspect we'll just make personal rules publicly visible. Long ago, transaction records were not as explicit or complete as they are today and you could sort of hide your "keep an eye on the suspicious interns" rules a little better, so this policy behavior wasn't totally silly, but it's almost impossible to actually hide any information now.

Ah, ok. I think that information is out of date with our current plans. Right now we (or maybe just I) see Nuance as a high risk product, one that is difficult to build and support/maintenance costs are completely unknown (and also likely very high). As such we're going to test a single connector (GitHub) and see how it performs / meets needs. Beside that, and maybe a basic email connector at some point, I don't believe we have plans for any other connectors. Nuance I think is a great product for the community to perhaps build and share connectors, though.

Thank you for the information.

A v1 of Nuance could be years away. see Planning.

What 3rd party apps ie. external sources (importers in your description) are you planning on supporting for v1 of Nuance?

Btw, we just ran into an issue where the Differential Revision wasn't parsed because the newline was just a LF, phabricator seems to require CRLF. So the git log shows it on its own line with the correct syntax but the description in the differential itself shows it all on one line. Another oddity...

This should maybe also somehow interact with Artifact Files.

We already provide a link in the form of the on Panels directly to the query.

Is this rule a lint-like rule, in the vein of T7617? See also T10523 for discussion of lint-like rules.

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