Page MenuHomePhabricator

Return milestone information in project.search
ClosedPublic

Authored by epriestley on Jan 8 2017, 7:32 PM.
Tags
None
Referenced Files
F18952717: D17153.diff
Wed, Nov 12, 6:25 AM
F18837463: D17153.id.diff
Mon, Oct 27, 5:35 AM
F18833790: D17153.diff
Sun, Oct 26, 5:48 AM
F18833676: D17153.diff
Sun, Oct 26, 5:06 AM
F18820835: D17153.diff
Oct 22 2025, 5:27 PM
F18777636: D17153.id41251.diff
Oct 11 2025, 4:06 AM
F18775680: D17153.id41257.diff
Oct 10 2025, 7:50 PM
F18702717: D17153.diff
Sep 28 2025, 1:08 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.