|
||||||||
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 |
- [JIRA] (JENKINS-14514) Repeatable jelly ta... b...@java.net (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... b...@java.net (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... b...@java.net (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... b...@java.net (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... e...@marketspulse.com (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... dogf...@java.net (JIRA)
- [JIRA] (JENKINS-14514) Repeatable jel... porter.bria...@gmail.com (JIRA)
Another candidate is the change to prevent ajax calls when the page is not visible.
I cannot find anything else in the changes from 1.473 to 1.474 that may have introduced this issue