Go to the Inventory tab for a Resource and edit, modify, then save its Connection Properties. Then click on the HISTORY button to view the connection properties revision history. There will be only one revision shown - the one corresponding to the update you just submitted. Instead, there should be two revisions listed - one for the initial version that was supplied by the plugin, and one for the user-submitted update. This will allow the user to rollback to the initial plugin config and will also make things consistent with the way the Resource config history works.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1404
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
Per triage this is moved to ONQA w/ the expectation that it is fixed. If not, please reopen, otherwise close
Tested on JON 2.4 GA Steps: 1) Log-in to JON 2) Goto inventory -> connection tab of Postgres/JBossAS 3) Click on EDIT and modify connection properties 4) Click on'SAVE' 5) Click on connection 'HISTORY' button Actual: Connection history has only one last modified version, there isn't initial version of connection history. Expected: Connection history should be two revisions listed - one for the initial version that was supplied by the plugin, and one for the user-submitted update. This will allow the user to rollback to the initial plugin config and will also make things consistent with the way the resource config history works.
I think this is still true. Not sure if we care though. Asking Heiko...
Users are used to the way it is now. I completely understand the idea behind the request and agree that it is useful, but do not think we should put much energy into it. Closing