The number of tracked data is in no time very large. When searching, therefore, a time restriction is necessary. Also searching by projects would be very useful.
Description
Description
Revisions and Commits
Revisions and Commits
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | epriestley | T5151 Allow to export query results from Phrequent | ||
| Open | epriestley | T5150 Extend query by time restrictions |
Event Timeline
Comment Actions
@epriestley What can I do to speed things up here? I've added a revision like you mentioned in D10162. But I get no feedback. Please let me know how I can help.
Comment Actions
There is nothing you can do to speed this up. See:
- T4778: When will my feature get built, or my bug get fixed?
- https://secure.phabricator.com/book/phabricator/article/prototypes/
- https://secure.phabricator.com/book/phabcontrib/article/feature_requests/#setting-expectations
- https://secure.phabricator.com/book/phabcontrib/article/contributing_code/#rejecting-patches
We are a very small team with a large number of users. Code costs time to review, upstream and support, and this isn't a priority for us right now.
Comment Actions
I'm just curious because of your comment, which was the reason for my last revision:
Search by IDs and Date Range: This is basically fine and can upstream immediately, but we should add (dateStarted) and (dateEnded) keys to the table. A couple of inlines. Separate this into a standalone diff and I can pull it after a couple tweaks. (https://secure.phabricator.com/D10162#86393)
But I get your point and I didn't read the links you've posted. Thanks!