There were no bugs which were reported as NeedInfo in the bug list. Creating a test bug to test that.
Created attachment 40496 [details] greasemonkey script This submitted script is not the best approach. The correct approach would have to be to get elements by class name 'bz_NEEDINFO' . Not sure what is the exact class name for needinfo bugs. Can some one set this bug to NEEDINFO so that I can fix the script and re-submit ? Thanks, ~Suren
Sure, set the needinfo on you.
You should also be sure it works when there is more than one keyword. Are you sure you should do a equality test, instead of a regex test? You should make sure that it will work even if the bug has more than one keyword.
Cedric, Thanks :) Ciao: Have fixed the issue with a different apparoach. Attaching a patch. If some one can verify if the patch works for you, I can close the bug :) Thanks, ~Suren
Created attachment 40563 [details] greasemonkey script version 0.2
Suren: Great stuff, thank you! :-) I have a feature request, if I can? It would be great if this script operated on this page (bug edit) too, and provided the following between the 'Additional Comments' text entry, and the Status combo box: - in case the bug is in the NEEDINFO state, it would provide a checkbox like '[ ] This comment provides the required information', that would clear the NEEDINFO + infoprovider: from the appropriate fields on pressing 'Commit' - in case it is not NEEDINFO, there would be a checkbox '[ ] Requires information from' followed by a text field for the email address; and if it was checked, it would add NEEDINFO to the Keywords and inforprovider:<the_email@from.the.text.field> to the respective fields on pressing 'Commit'
Hi Kendy, Got it. Shouldn't be tough. But has to be another Greasemonkey script, not the part of same one as they have different URL patterns. Will try to get that done and attach a patch. Thanks, ~Suren
Created attachment 48115 [details] NeedInfo/EasyHack insert/delete for show_bug + product=>LibreOffice Developed a new BugZilla grease script that operates as load event hendler and: 1) selects Product option LibreOffice on query page 2) adds Set/Clear NeedInfo and EasyHack buttons on show_bug page. These buttons insert/delete markers in keywords, whiteboard and summary. Handles various current formats of [ EasyHack(s) : ] markers on the summary. This version does not highlight NeedInfo bugs in the result page to avoid background download of all NeedInfo bugs on each query result (buglist) page. Future Possibilities: 1) Bring back NeedInfo highlighting as option on query result page. Add button to add highlighting to current result so background load of NeedInfo bugs only occur on request. Could be further enhanced to store list on browser and only thereafter download NeedInfo bugs changed since previous load (i.e. in last minutes or hours). 2) Add buttons to query page to insert/delete select conditions on the query page for NeedInfo (onlyNI/excludeNI/don't care about NI) and other useful selects. Can see divergence of qa and dev needs re select fields and conditions on query. Maybe add qa/dev mode switch. 3) Add Edit Last Search button to show_bug page to open query page in new tab. 4) Integrate Cedric's script -- http://userscripts.org/scripts/show/87923 -- to create relation to commits on branches for qa to know where to test features & fixes as they move toward/into release. 5) Add Recent lists for bugs and searches stored on browser or in session cookies. 6) .. other ideas -- Any other scripts out there? Developed using Opera and may not work well in other browsers. Uploaded to http://userscripts.org/scripts/review/104918 for testing as FireFox Greasemonkey script. Please let me know what other forms of grease you need, and of any lumps in the lubricant here...
Put in some brackets and a colon for testing EasyHack button.
Created attachment 48118 [details] Set/clear for NeedInfo+EasyHack markers on show_bug Fixed leftover bracket issue where summary became EasyHack: ] ]. Before I lose another half-day on ']' just added code to chew them off the front after removing EasyHack(s)...
Add to list of work: 0) Add an OnSubmit listener that rips back out all the nodes inserted by the script in order to avoid confusing BugZilla on form submission.
Created attachment 48293 [details] greasemonkey helper for qa/dev New script version adds submit handler that strips out form elements whose values will be sent on submission. No evidence that BugZilla has problems with extra info: added for safety.
Created attachment 48306 [details] helper script for qa/dev removed alert
remove obsolete tags
Do we still need this? We have NEEDINFO status now ... or do I missing something?
Deteted "Easyhack" from summary
Joel/Joren: is this tracker still relevant?
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility. see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
setting this to invalid. several pings remained unanswered and it doesn't look like this test bug is still needed. if i'm making wrong assumption, please reopen.
Indeed, not necessary any more, the freedesktop bugzilla got support for NEEDINFO in the meantime.
Migrating Whiteboard tags to Keywords: (EasyHack) [NinjaEdit]
Remove LibreOffice Dev List from CC on EasyHacks (curtailing excessive email to list) [NinjaEdit]