|
||||||||||||||
|
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.
AFAICT we're using priorities mostly consistently with the JIRA definitions, and this isn't Crashes, Loss of Data, Severe Memory Leak. Reducing to Major – while a workaround is present (indicating Minor actually), it prevents operation of Jenkins entirely if unknown, so that looks like a reasonable compromise.
(FWIW I've asked that the default be set to Minor so that going Major is already a step above the default – no success so far![]()
)