Sheriff bot files bugs using commit queue account. You need to scroll down and find the reporter e-mail address in a comment (where it's not highlighted). This is quite annoying. Also, the Reporter field is sent in RSS feeds, but comments aren't.
Since many people are going to read a bug, and filing it is a one-time act, I'm not sure if any time is saved for project contributors as a group.
See also: bug 59545. Would it make sense to roll out the patch from bug 59491 until these are resolved?
I've posted a fix to bug 59545.
I don't know any way to fix this. We can certainly make the requester much more obvious in the description (or even in the bug title). But I don't know any way to change the reporter of a bug once created.
I wonder if what is mentioned in this redhat bugzilla comment is possible:
I don't see any way to change the reporter in http://trac.webkit.org/browser/trunk/Websites/bugs.webkit.org/process_bug.cgi (which is the form that bugzilla posts when editing a bug).
If we found a way to fix this, we could easily fix this for all bugs that sheriff-bot creates. Including the rollout bugs (which are currently much more common than the new create-bug bugs).
The sheriff-bot currently files all bugs (rollouts as well as these new create-bug bugs) as email@example.com. Which is one account which is shared between many of the EWS bots and the sheriff-bot.
I'm happy to get him his own account (firstname.lastname@example.org?) if that would make this any better.
The sheriff-bot has failed a total of 581 bugs so far in its lifetime:
> I'm happy to get him his own account (email@example.com?) if that would make this any better.
I don't think that would be a significant change.
Looking at the bugs filed by sheriffbot, I think that they are generally of lower quality than it used to be common for the project. They don't even have a component set.
(In reply to comment #8)
> > I'm happy to get him his own account (firstname.lastname@example.org?) if that would make this any better.
> I don't think that would be a significant change.
> Looking at the bugs filed by sheriffbot, I think that they are generally of lower quality than it used to be common for the project. They don't even have a component set.
I'm happy to implement suggested ways to improve the quality of bugs filed by any of our tools.
For example, I'd be happy to have rollout bugs copy the component from the bug they're rolling out if that would be of help?
That sounds like a neat idea.
Personally, I don't care about rollout bugs much - they are not something many people are going to read, and it is obvious from the title what kind of bugs those are. But filing new real bugs from a single line command in chat doesn't seem so great.