flaky finding of references
- cool factor lists the tickets that are tagged with it, but polish doesn't (though they both includes the same Auto card!). The one that is listed on polish - i went to that card, removed the polish pointer, then added it back again. Then it showed up - weird.
- had this issue with the todo query on the home page of the staff wagn
- happens with many of the Decks on Wagn.org, including Permabit wagn. There are several tickets that are tagged with "Anon1" (search for it), but none of them show up on the tickets query on the Permabit wagn card. Anon1 used to be a basic card, but the links stopped working when I changed it to a "Deck." If you go to one of the taglist cards that point to it and edit it, when it saves the reference is evidently restored (and the Anon1 card's query will reflect the change).
- might be a different one, but I renamed Hooze to Hooze+about, and opted to have it *NOT* update the links refering to it (I still wanted them to refer to Hooze), but it updated them anyway. Saw this several times in a row
Related support tickets:Relevant user stories:add oneTags:
one thing to test is references from a card getting updated correctly when its name or type is changed.
John, I know Lew did a bunch of work on this right before the connectipedia launch, but I don't think he ever came back and tested. Can you have a look at these issues and tell me where you think we are?
--Ethan McCutchen.....Thu Jul 03 16:49:38 -0700 2008
Still a problem. This search via WQL shows 19 Tickets tagged with polish:
...but a regular search shows well more than that: http://wagn.org/search/polish
--John Abbe.....Thu Jul 03 21:19:34 -0700 2008
We definitely still have bad data (unrecorded references), but I'm not sure the code bug is still there. References only get recorded when cards are saved, so any cards that have not been saved since the last code fix may still be busted.
John, I went ahead and changed all the tickets this thing points to to you and tagged them with Wagn 0.10.
Lew, do you think it might be worth regenerating all the references in the migration?
-e
--Ethan McCutchen.....Sun Jul 13 16:42:29 -0700 2008
Someone wrote: this may be yet another ticket, but we have never implemented inclusion updates upon a name change.
Yup, the ticket exists - update inclusions when renaming)
--John Abbe.....Mon Jul 14 00:38:53 -0700 2008
maybe make a rake task for updating the references
--Lewis Hoffman.....Wed Jul 16 16:26:56 -0700 2008
That would be great. If you run it on wagn.org, i will check the results.
--John Abbe.....Thu Jul 24 11:28:33 -0700 2008
I checked on the Anon1 issue above. on sandwagn.wagn.org created Fuzzy (basic), pointed 3 tickets to it, changed the type to Deck. All tickets still there.
--Lewis Hoffman.....Thu Jul 24 18:56:05 -0700 2008
Also did some basic tests of references from an item being updated an those seemed fine.
--Lewis Hoffman.....Thu Jul 24 18:56:38 -0700 2008
I created a rake task db:references:update_all and ran it on wagn.org. The closest thing I could find on the flaky references was that clearing the cache of the old entry on cascaded renames wasn't working. that's fixed now.
--Lewis Hoffman.....Thu Jul 24 20:57:00 -0700 2008
Sounds good to me. closed.
--John Abbe.....Sun Jul 27 12:14:18 -0700 2008
Notes