|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Well, that depends on how the default assignee (or component lead) would like to work with such issues. (Which requires that we have a component lead willing to fix all those issues![]()
With a component the issues are automatically assigned. With a label they are not (the label is also a free text field with code completion, e.g. we have ux and user-experience). I just want to be sure that my issues don't get lost in the enormous amount of open core issues.