Page MenuHomePhabricator

Fix an issue where tokenizers can sort milestone results into the wrong query phase
ClosedPublic

Authored by epriestley on Dec 9 2016, 2:11 PM.
Tags
None
Referenced Files
F14370252: D17013.id40932.diff
Fri, Dec 20, 5:46 PM
F14370221: D17013.id40936.diff
Fri, Dec 20, 5:42 PM
Unknown Object (File)
Sun, Dec 8, 3:57 PM
Unknown Object (File)
Sat, Nov 30, 12:13 PM
Unknown Object (File)
Tue, Nov 26, 11:51 PM
Unknown Object (File)
Fri, Nov 22, 9:32 PM
Unknown Object (File)
Nov 17 2024, 8:42 PM
Unknown Object (File)
Nov 16 2024, 10:37 AM
Subscribers
None

Details

Summary

Fixes T11955. Currently, milestones have an internal name of "Parent (Milestone) ...".

This makes them look like they're prefix matches for "Parent", but they're actually prefix matches for "Milestone".

Reorder the names so that the internal name is "Milestone Parent ...".

Test Plan

Created a project "AAA" with milestone "BBB". Searched for "AAA", found "AAA" and milestone "AAA (BBB)".

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Fix an issue where tokenizers can sort milestone results into the wrong query phase.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Dec 9 2016, 4:03 PM
This revision was automatically updated to reflect the committed changes.