See the attached screenshots for examples of where its impossible to differentiate between the resources in the group which are being operated on.
It doesn't have to be a new parent resource column, but it should be something which makes the resource name more unique.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1114
Imported an attachment (id=368494)
Imported an attachment (id=368495)
Jay took care of this - [master 23768b7]. Note, disambiguation was needed for the group op history details view (e.g. #ResourceGroup/10401/Operations/History/10161), which includes a table of the member history items, but it was not needed for the group op schedule view, which does not display any per-member info.
while verifying this, i encountered an error scheduling group operations. ora-02289. i logged new bz 701272.
marking this verified...RHQ4 Master branch. I created a compatible group with 6 resources of the same type (EJB beans) and scheduled an operation (view stats) which repeated frequently over the course of several minutes on the group. In view operations history, I could distinguish between each operation history and determine on which resource the operation executed.
Bulk closing of old issues that are in VERIFIED state.