Yesterday I reviewed all of our launchpad-gm-scripts scripts in light of Launchpad's recent UI changes. I was a bit surprised to see half the scripts work fine, but disappointed that half show some breakage.
I fixed my buttontags script, which was not able to apply tags, and filed bugs 245042 and 245048 for the other two bugs caused by the Launchpad update.
As well, since I expect we are likely to experience future sudden Launchpad interface changes, I've written up a TESTING file to hopefully help folks doublecheck the scripts still work in such situations. Wish there was some way these tests could be done prior to new Launchpad UI updates, but lacking that we'll just have to beg forgiveness for the inevitable breakages.
If you're not yet using the Launchpad greasemonkey scripts, here's a quick plug for them, and list of what they do:
lp_buttontags.user.js - Shortcut for applying several standard tags on bugs
lp_highlight_me.user.js - Highlights your items on the +milestones page
lp_karma_suffix.user.js - Displays user's karma next to their username. Handy to spot new users vs. experienced ones.
lp_patches.user.js - Stars attachments which are patches
lp_stockreplies.user.js - Mechanism for storing and applying a set of stock replies (which you can define) to bugs, updating status dropdowns, etc. as well.
lp_workflowreports.user.js - Identifies workflow reports.
It's not a bad idea. I think a lot of us are fairly caught up in our own work, so don't think to check against staging.
In any case, I added a TESTING document to the launchpad gm scripts package listing in paint-by-numbers fashion how to check the scripts. My hope is that if anyone knows of a UI change, this'd make it pretty easy to run through and check basic functionality of everything really quick.
I'm also interested in exploring greasemonkeylaunchpad-2.0-api uses, as I think that'd let us bypass a lot of the UI change problems. (Just depends on the API being stable...)