|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Well... that's bad.
We're currently discussing changes to Jira on the jenkinsci-dev mailing list that would explicitly remind people that Jira is only for bug reports and change requests (and not for requests for assistance) right on the report form. So far, nobody has spoken up against it, so that opinion seems to be the general consensus. Jason is of course free to contribute to that discussion, or start a more fundamental one (or put it on the agenda for the next project governance meeting). FWIW the wiki page on using Jira also never mentions requests for assistance as a valid use case for it.
While there's certainly some leeway in how a component owner deal with reports for his/her component, the problem in this case is that inconsistent instructions on how to use JIRA (or different rules per component) will only lead to confusion (on the reporters' part) and frustration (for them and the developers handling issue reports that aren't), so adopting a consistent policy would be best.
I agree with Jason that wiki comments suck. However, requests for assistance are best handled via the jenkinsci-users mailing list, not Jira.