|
||||||||
|
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.
JENKINS-7824 (claim assignment) is a good idea and I will implement that.
Not a fan of this though.
I think Claim should remain a human action as anything else devalues it. I feel that many developers would simply ignore "claims" if they are systematic for this reason. Crucially, auto-assigning to a poor tech-lead means he cannot differentiate real Claims from the noise of failed builds.
Lastly, with a good dashboard, claimed failures are clearly distinguished from unclaimed failures so the cue for aforementioned tech-lead to "assign" the failure is there already. See https://github.com/jan-molak/jenkins-build-monitor-plugin