@calfzhou see D12526, and then https://gerrit.wikimedia.org/r/#/c/207415/3/src/view/reports/SprintReportOpenTasksView.php as an example to how to fix it.

Thanks, this is certainly useful. I didn't know phabricator was assumed to be always unstable, I might have skipped that part of the documentation.

@btrahan I understand that, but it also may be in PH interest to not break third party extensions without announcing it.

@epriestley, @bluehawk are you aware if https://secure.phabricator.com/rP83db5965ab6c640864fb8b66d813369274d40594 broke this extension? I don't always use the latest PH, but some days ago I updated it to the latest and I couldn't get into any tasks anymore as they would raise Unhandled Exception ("PhabricatorDataNotAttachedException") when trying to access them. I suspect that commit is the root cause as it also affected wikimedia and caused the same exceptions to happen, but they are using a different sprint extension. Plus, reverting phabricator to one commit before that makes the issue disappear.

To contribute to this, some months ago we moved from a LiquidPlanner instance with a few thousand tasks to PH. From what I remember now, if conduit was a bit more powerful it would be a lot easier to do such things (it's almost like if PH don't want people to migrate from other systems into PH). The basic things missing from conduit, last time I looked at it, was the ability to specify dates other than the current one for any action you do (e.g. task creation date, comment date).

Thanks, see D10480 for a more complete approach to that.

The single letter example was... an example.

If the search was better I would agree with that; at this point I don't see what's the purpose for the People page. If I want to find people that need to be verified, there's a query for that, but if I actually want to find people then it's not possible.

Except in those cases where you are not sure about the exact name (which I would say is the reasoning behind even starting T6092), if I enter "pg" it doesn't show "g-p-g", if I enter "gp" it shows someone else with username "gpg".

It's useful for me to have sorting as it's easier to go through the list and find people. It seems obvious to me that A to Z ordering by username excluding disabled users should be the default query (exactly like is done in Projects which excludes archived ones in the default query), and then you could allow sorting my creation date and others.

@bluehawk don't want to annoy you over this, but did you check if that issue was a feature and not a bug? I have been using the extension, works fine for me. Thanks for doing it.

The current sorting option doesn't make any sense when dealing with people, that's the motivation behind this.

Also, this is not random access, it's "alphabetical" access.

epriestley, the use cases you're mentioning are already covered by the search features available for the People app (joined after, joined before); the one I'm mentioning is not. There's also a page only for the Approval Queue, which doesn't need to be modified.

Thanks, is this closer to what we're all after?

I really think the question is a different one, how could the current behavior be useful or consistent with other areas? For instance, you don't get to sort projects but they are ordered alphabetically. Have you used an address book sorted by creation date, and how helpful was that?

Are you considering Bitcoin for this?

In T6013#10, @epriestley wrote:

In particular, I can see the file you uploaded just fine because I can see this task, even though the view policy is restrictive.

In T5051#53, @bluehawk wrote:

@g-p-g Do you mind sending a screenshot of the data section (with points closed per day, etc.) on the one that goes negative?

@bluehawk please ignore the first three screenshots above, I'm not sure how but I completely missed the dates in the plots. The auto-generated sprints are still running :)

@bluehawk my only issue with it so far are the plots auto-generated.

@bluehawk that looks interesting, I'll give it a try next week. Thanks for putting this up.