|
||||||||
|
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.
I really doubt anyone is actively ignoring this issue. If you're referring to me reducing priority, please note that before I reviewed most of the unresolved core issues in this tracker, we had dozens and dozens of blocker/critical core issues (in many cases, just like this one, they weren't actually that severe), and nobody cared about those either. It's not like an alarm goes off somewhere whenever an issue with high "priority" gets filed.
As far as I can tell, priority is given to regressions, issues affecting many users, and issues that the developers themselves want to see fixed (and, in the case of Cloudbees employed Jenkins devs, issues from customer support requests). This issue seems to be none of the above.