Fix a bug where "View as Query" could replace a saved query row by ID, causing…


Fix a bug where "View as Query" could replace a saved query row by ID, causing workboard 404s

Fixes T13208. See that task for details.

The clone $query line is safe if $query is a builtin query (like "open").

However, if it's a saved query we clone not only the query parameters but the ID, too. Then when we save() the query later, we overwrite the original query.

So this would happen in the database. First, you run a query and save it as the workboard default (query key "abc123"):


Then we clone it and change the parameters, and save() it. But that causes an UPDATE ... WHERE id = 123 and the table now looks like this:


What we want is to create a new query instead, with an INSERT ...:


Test Plan:

  • Followed reproduction steps from above.
    • With just the new save() guard, hit the guard error.
    • With the newCopy(), got a new copy of the query and "View as Query" remained functional without overwriting the original query row.
  • Ran migration, saw an affected board get fixed.

Reviewers: amckinley, joshuaspence

Reviewed By: joshuaspence

Subscribers: PHID-OPKG-gm6ozazyms6q6i22gyam

Maniphest Tasks: T13208

Differential Revision: https://secure.phabricator.com/D19768