1. Open a job configuration that has a conditional build step defined in it, with the Chrome browser (Firefox does not show this problem).
2. Click the back button to navigate away from the config.
3. Click forward to go back to the config.
4. The conditional build step settings will be blank/default, but all other job configuration remains correct.
This is a really nasty bug, I've had a number of users accidentally break their configs without realizing it, because if you save after this happens you lose the conditional build step settings. Luckily the Job Config History plugin makes it easy for us to undo this.
|Field||Original Value||New Value|
|Component/s||core [ 15593 ]|
|Component/s||conditional-buildstep [ 15947 ]|
|Assignee||Dominik Bartholdi [ domi ]|
|Summary||Navigating back, then forward, from a job configuration causes loss of config data in Chrome||Navigating back, then forward, from a job configuration causes loss of config data|
|Priority||Major [ 3 ]||Critical [ 2 ]|
|Assignee||rsandell [ rsandell ]|
|Remote Link||This issue links to "Pull Request (Web Link)" [ 14644 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Workflow||JNJira [ 149742 ]||JNJira + In-Review [ 193271 ]|
|Remote Link||This issue links to "CloudBees Internal OSS-298 (Web Link)" [ 18920 ]|