Page MenuHomePhabricator

Return milestone information in project.search
ClosedPublic

Authored by epriestley on Jan 8 2017, 7:32 PM.
Tags
None
Referenced Files
F18381945: D17153.id41251.diff
Thu, Aug 28, 8:41 PM
F18374854: D17153.id41251.diff
Thu, Aug 28, 9:16 AM
F18374658: D17153.id.diff
Thu, Aug 28, 9:05 AM
F18091337: D17153.id41251.diff
Wed, Aug 6, 9:10 PM
F18089787: D17153.id41257.diff
Wed, Aug 6, 12:36 PM
F18082805: D17153.id.diff
Tue, Aug 5, 7:32 AM
F18054739: D17153.diff
Mon, Aug 4, 6:37 AM
F17866939: D17153.id41257.diff
Jul 28 2025, 5:12 AM
Subscribers
None

Details

Summary

Ref T12074.

  • project.search now returns milestones by default.
  • A new constraint, isMilestone, allows filtering to milestones, non-milestones, or both (API and web UI).
  • project.search now returns a milestone number for milestones, or null for non-milestones.
NOTE: Existing custom saved queries in projects which previously did not return milestones now will. I expect this to have little-to-no impact on users, and these queries are easy to correct, but I'll note this in changelogs.
Test Plan
  • Ran various queries with project.search and in the web UI, searching for milestones, non-milestones, and both.
  • Web UI default behavior (no milestones) is unchanged, but you can now get milestones if you want them.
  • Queried a milestone by ID/PHID via API.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Jan 8 2017, 7:51 PM
This revision was automatically updated to reflect the committed changes.