User talk:GeneralNotability/spihelper/Archives/2020/July
 | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
UX question to folks using the script
I'm planning to change the script so that it operates per-case (so if there are multiple cases on the page, you select which one you want to change). This will be necessary for the "request CU action," "comment," and "close" actions (since those explicitly affect one section at a time), but how would you all like it to work for "block/tag" and "archive"? I could see arguments both for "make them act on all eligible items" (e.g. archive all closed, display all blockable/taggable) and "make them only operate on one section". How would you all prefer things work? The general look I'm planning on, by the way, is that the top-level SPI menu will get a drop-down in which you select the case you want to modify. GeneralNotability (talk) 15:06, 13 July 2020 (UTC)
Workflow update incoming
Hey folks, I've redone the handling for case status changes (by merging the mutually exclusive "Act on CU request" and "Request CU or other action" actions). This should make things easier to maintain under the hood and cut down on some duplicate code (and, more importantly, get rid of the annoying fact that we had two buttons which basically did the same thing). As part of that, I've made some workflow changes (for example, you can no longer move a case to "relist" if it was never checked). I've tried to be smart about the possible states you can move between, but it's possible I missed a corner case. Let me know if you run into a situation where you expected to be able to move a case to a particular state but weren't able to. GeneralNotability (talk) 02:51, 22 July 2020 (UTC)