On 13.06.2018 08:26, Oliver Kurz wrote:
I do not even think it is possible to "make a bug open". At least I can't uncheck the according check box for closed bugs :(
Check the SUSE-Internal Bugzilla docs (ten years ago, there were some ;-) A closed bug is closed. It gets closed long after it has been RESOLVED FIXED (or whatever resolved state it got). Then you cannot reopen it. At least that's how I remember it from said docs. What we are discussing here, is changing the product or the access restrictions, to "opening it up to the community", regardless of it's NEW/IN_PROGRESS/NEEDINFO/RESOVED/CLOSED database status.
The best *I* could do is either copy-paste relevant content to an email or clone the bug to an "open" product, e.g. openSUSE Tumbleweed
My question was: do I get an response after sending my mail to opensuse-bugshare or do I have to manually check all the bugs I complained about? If I have to check these manually, I will have to invent something to automate this. If I would need to create something™ to automate bugzilla interaction, this would of course be a welcome opportunity to extend it to automatically check on all mentioned bugs in the patchinfo and automate the opensuse-bugshare mails... :-P (which, until today, were all sent manually) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org