[opensuse-buildservice] reporting bugs against buildservice projects/packages now possible
Hi all, I just enabled the link to bugzilla in the OBS webclient. It uses a new role called 'bugowner' to determine the assignee of a reported bug. Bugowner roles can be given by using the [Add User] link in the webclient, or adding another <person/> element using osc. As soon as a bugowner is set, a link called [Report Bug] appears below the description on the project/package pages. Clicking this link will open the bugzilla new bug form with product, category and assignee preset to the (hopefully) correct values. Packages inherit the bugowner role from their project like the maintainer role. The role is not propagated through namespaces though. It is possible to set more than one bugowners, although currently it doesn't make much sense. A single assignee is picked more or less randomly from the available ones. Comments welcome, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Dec 12, 2007 at 02:58:43PM +0100, Andreas Bauer wrote:
Hi all,
I just enabled the link to bugzilla in the OBS webclient. It uses a new role called 'bugowner' to determine the assignee of a reported bug. Bugowner roles can be given by using the [Add User] link in the webclient, or adding another <person/> element using osc.
As soon as a bugowner is set, a link called [Report Bug] appears below the description on the project/package pages. Clicking this link will open the bugzilla new bug form with product, category and assignee preset to the (hopefully) correct values.
Packages inherit the bugowner role from their project like the maintainer role. The role is not propagated through namespaces though.
It is possible to set more than one bugowners, although currently it doesn't make much sense. A single assignee is picked more or less randomly from the available ones.
Is the bugowner the E-Mail Address or the Novell login name? Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Marcus Meissner wrote:
Is the bugowner the E-Mail Address or the Novell login name?
The novell login name. This way we can ensure that the used e-mail address is accepted by bugzilla as assignee.
Ciao, Marcus
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Marcus Meissner wrote:
Is the bugowner the E-Mail Address or the Novell login name?
It's the login name. Eg: $ osc meta pkg server:database mysql | grep bug <person role="bugowner" userid="michal-m"/> Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 12 December 2007 14:58:43 wrote Andreas Bauer:
Hi all,
I just enabled the link to bugzilla in the OBS webclient. It uses a new role called 'bugowner' to determine the assignee of a reported bug. Bugowner roles can be given by using the [Add User] link in the webclient, or adding another <person/> element using osc.
cool stuff :) Esp. projects with lots of different contributors like KDE:Community should use that to define a bugowner for each package ... bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 12/12/2007 at 3:58 PM, Andreas Bauer <abauer@suse.de> wrote: Hi all,
I just enabled the link to bugzilla in the OBS webclient. It uses a new role called 'bugowner' to determine the assignee of a reported bug. Bugowner roles can be given by using the [Add User] link in the webclient, or adding another <person/> element using osc.
Very nice... hope people will use it in a good way. But this means: only people with a OBS Account are able to report a bug in a package? I think it would be good to have a Report Bug link also on the software.o.o/search interface. Is more likely that an end user get's a packet from there.
As soon as a bugowner is set, a link called [Report Bug] appears below the description on the project/package pages. Clicking this link will open the bugzilla new bug form with product, category and assignee preset to the (hopefully) correct values.
Would it be possible to have the summary preset to someting like [project/package]? Otherwise it can end up quiet fast that noone knows exactly where from the bug comes; the package is most likely readable from the report, but it could be in several projects.
Packages inherit the bugowner role from their project like the maintainer role. The role is not propagated through namespaces though.
What is your suggestion? Should it be as 'fine grained' as possible, so that I set myself as bugowner of all 'my' packages (which are some in the OBS, spread over several projects), or would it be better for the 'projects' to elect somebody that is making bug triage, and assigning to the owner of the packets later? Thanks for the great work! Dominique -- Sorry for the annoying disclaimer that follows. TMF is a global management and accounting outsourcing firm with 77 offices in 60 countries and over 2,500 professionals (2007). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 12 December 2007 15:22:29 wrote Dominique Leuenberger:
Hi,
On 12/12/2007 at 3:58 PM, Andreas Bauer <abauer@suse.de> wrote:
Hi all,
I just enabled the link to bugzilla in the OBS webclient. It uses a new role called 'bugowner' to determine the assignee of a reported bug. Bugowner roles can be given by using the [Add User] link in the webclient, or adding another <person/> element using osc.
Very nice... hope people will use it in a good way. But this means: only people with a OBS Account are able to report a bug in a package? I think it would be good to have a Report Bug link also on the software.o.o/search interface. Is more likely that an end user get's a packet from there.
we do not want to expose the email adress to the public to avoid spam. So only logged-in users shall see it. software.o.o has not yet an authentification mechanism, this comes later and than we can also a bugreport link there. However, we wanted to create a link from software.o.o to build.o.o to allow bugreporting via one more indirection for now. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, on Mittwoch, 12. Dezember 2007, Adrian Schröter wrote:
On Wednesday 12 December 2007 15:22:29 wrote Dominique Leuenberger:
[...] I think it would be good to have a Report Bug link also on the software.o.o/search interface. Is more likely that an end user get's a packet from there.
we do not want to expose the email adress to the public to avoid spam. So only logged-in users shall see it. software.o.o has not yet an authentification mechanism, this comes later and than we can also a bugreport link there.
There was a discussion some time ago to have a small redirector script on bugzilla.novell.com which takes the iChain username as parameter and redirects to enter_bug.cgi with the mail address as parameter. (No need to hack bugzilla, just a standalone script that enforces login, queries iChain for the mail address and does a redirect to enter_bug.cgi pre-populated with the assignee etc.) An advantage would be that the login would happen on *.novell.com, avoiding the need to login two times (on build/software.o.o and bugzilla.novell.com). Another advantage: The buildservice could include the "report bug" URL in the packages (Example: "Packager: http://bugzilla.novell.com/obsbug.cgi?user=cboltz&package=foobar-1.42") Is this possible?
However, we wanted to create a link from software.o.o to build.o.o to allow bugreporting via one more indirection for now.
Yes, it's a good start. Some minor issues: The project page is inconsistent regarding linebreak. home:cboltz now looks like this: [Watch this project] [Create Subproject] [Delete Project] [Report Bug] -> please decide if you want all links in one line (like on the package page) or add another line break between the last two links Can the bugreport be pre-populated with the project and package name? For example, add something like this to the "report bug" link: ...&comment=home:cboltz%20package_name%201.42 (maybe this should even go into the summary - opinions?) Regards, Christian Boltz --
Wieso ich, ich habe 1,5 Mbit anbindung, ständig. Du? Oder dein Rechner? :-) Was meinst du wie ich nach 1,500,000 Bit aussehe, glaubst du, dann könnte ich noch schreiben, geschweige denn programmieren? [> Ratti und Gerald Goebel in fontlinge-devel]
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Mittwoch, 12. Dezember 2007 15:22 schrieb Dominique Leuenberger:
As soon as a bugowner is set, a link called [Report Bug] appears below the description on the project/package pages. Clicking this link will open the bugzilla new bug form with product, category and assignee preset to the (hopefully) correct values.
Would it be possible to have the summary preset to someting like [project/package]? That would be nice, can be done by adding a short_desc=foo parameter to the url.
Klaas -- Klaas Freitag Architect OPS/IPD SUSE LINUX Products GmbH - Nuernberg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, On Wed, Dec 12, 2007 at 03:22:29PM +0100, Dominique Leuenberger wrote:
On 12/12/2007 at 3:58 PM, Andreas Bauer <abauer@suse.de> wrote: I just enabled the link to bugzilla in the OBS webclient. It uses a new role called 'bugowner' to determine the assignee of a reported bug. Bugowner roles can be given by using the [Add User] link in the webclient, or adding another <person/> element using osc.
Very nice... hope people will use it in a good way. But this means: only people with a OBS Account are able to report a bug in a package? I think it would be good to have a Report Bug link also on the software.o.o/search interface. Is more likely that an end user get's a packet from there.
I would also appreciate that. At the moment, the buglink is primarily visible to the package maintainer himself (who might even be the bugowner himself).
Would it be possible to have the summary preset to someting like [project/package]?
Great idea. That seems rather necessary to me. Another question is, do projects need a "report bug" link, or should only packages get one? Isn't a reported bug always about a package? Would one ever report a bug about a project? Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Dr. Peter Poeml wrote:
Another question is, do projects need a "report bug" link, or should only packages get one? Isn't a reported bug always about a package? Would one ever report a bug about a project?
I think there's place for both: * Please also build for $dist * Can't build against your repositories, please fix your _config * Bugs about patterns * Bugs about unresolved dependencies / other problems with installing from the repository, where the culprit might not be obvious Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Dec 17, 2007 at 11:01:13AM +0100, Michal Marek wrote:
Dr. Peter Poeml wrote:
Another question is, do projects need a "report bug" link, or should only packages get one? Isn't a reported bug always about a package? Would one ever report a bug about a project?
I think there's place for both:
- Please also build for $dist
- Can't build against your repositories, please fix your _config
- Bugs about patterns
- Bugs about unresolved dependencies / other problems with installing from the repository, where the culprit might not be obvious
You are right -- that are all use cases for a "bug link" which I can think of, too. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Hi,
On 12/12/2007 at 3:58 PM, Andreas Bauer <abauer@suse.de> wrote: Hi all,
I just enabled the link to bugzilla in the OBS webclient. It uses a new role called 'bugowner' to determine the assignee of a reported bug. Bugowner roles can be given by using the [Add User] link in the webclient, or adding another <person/> element using osc.
As all reports are comming from the OBS, and authorization is done by both interfaces (obs and bugzilla) by IChain, is it possible to have a 'single sign on' between those two sites? Dominique -- Ignore from here on... TMF is a global management and accounting outsourcing firm with 77 offices in 60 countries and over 2,500 professionals (2007). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-12-12 15:24:35 +0100, Dominique Leuenberger wrote:
As all reports are comming from the OBS, and authorization is done by both interfaces (obs and bugzilla) by IChain, is it possible to have a 'single sign on' between those two sites?
afaik we can only support SSO on the same domain (opensuse.org/novell.com) but not across those. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Great feature ! I tried it for my home-project and it works fine. Just one comment: "3rd party / Buildservice" would be more precise than "3rd party software" I think ... i mean it would make things more obvious. Well done ! Best regards -- Jan-Simon Möller --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (10)
-
Adrian Schröter -
Andreas Bauer -
Christian Boltz -
Dominique Leuenberger -
Dr. Peter Poeml -
Jan-Simon Möller -
Klaas Freitag -
Marcus Meissner -
Marcus Rueckert -
Michal Marek