There's now a set of settings to control what issue status values show up in the default issue queue queries. This should match the ones on d.o.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | do_testing_issue_status.patch.txt | 3.11 KB | dww |
There's now a set of settings to control what issue status values show up in the default issue queue queries. This should match the ones on d.o.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | do_testing_issue_status.patch.txt | 3.11 KB | dww |
Comments
Comment #1
dwwThere's something fishy going on with drupal_execute() here. After I add the new status values, if I just try to modify the existing ones, it ends up clearing the "default query" bit on the "patch (to be ported)" status that was just added. It's as if some state is getting cached in form building land and subsequent calls to drupal_execute() are seeing the old values, not the current values. :( So, there's a minor hack in this patch where we add the new status, and then when we go to modify the existing ones, we set the "default query" bit on "patch (to be ported)" again.
I don't have the time or energy to dig too deeply, and this patch works. I'm inclined to just commit it, and if someone wants to dig into this little weirdness later, they should feel free to do so.
Any objections?
Thanks,
-Derek
Comment #2
webchickSounds fine to me; tested, works.
Comment #3
dwwCommitted to HEAD.
Comment #4
(not verified) commented