Milestone changes not reflected in cached tickets

[DavidDudson]

If a ticket is downloaded with Milestone X and then updated later to Milestone Y.
You still have to search via mil:X.

Note the tickets in question was also closed between the download and milestone update.

[lukeu]

Incremental change detection happens on the Trac ticket's modification timestamp.

How were the relevant ticket milestones updated? If they were definitely made through the Trac Web interface then this could be a bug.

However if (for example) somebody circumvented Trac by making a bulk database edit directly (without 'touching' the ticket timestamp for consistency) then TI wouldn't support that. You'll just need to click "Connect" and re-download the ticket data fresh to workaround.