|
||||||||
|
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.
That is not really a constructive comment Kanstantsin. Several of us on this bug do not see it as useless complexity.. Naming our jobs "default" is not really a feasible practice. Especially if we have multiple different projects going on in our jenkins install.
Having the ability to simply define what name we want it allows a better workflow especially when other systems are involved that look at these status values on github commits. We all have legitimate reasons for needing a customizable name for this status context.. IMHO this should be logged as a new issue so we can further discuss the needs there as a separate enhancement.