[JIRA] (JENKINS-14030) renaming a job does not preserve history
Brian Sipos commented on JENKINS-14030 renaming a job does not preserve history When I rename a job in current version (1.496) the job history disappears immediately, but if I restart the Jenkins service the history reappears under the new job name. Internally, the history files are being moved properly but jenkins doesn't re-load the data into the new project. 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-14030) renaming a job does not preserve history
m_broida commented on JENKINS-14030 renaming a job does not preserve history Similarly: renaming (or deleting) a node causes job history entries for jobs built on that node to say they were built on the "master" node instead. 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-14030) renaming a job does not preserve history
bnovc created JENKINS-14030: --- Summary: renaming a job does not preserve history Key: JENKINS-14030 URL: https://issues.jenkins-ci.org/browse/JENKINS-14030 Project: Jenkins Issue Type: Bug Components: core Reporter: bnovc When you rename a job, the history on the job is lost. I don't see any reason why this should happen and should at least be a choice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
