Bug 30228 – Right-click in LDAP directory performs operation on the wrong object

Bug 30228 - Right-click in LDAP directory performs operation on the wrong object


Summary:	Right-click in LDAP directory performs operation on the wrong object

Status:	RESOLVED DUPLICATE of bug 26062

Product:	UCS
Classification:	Unclassified
Component:	UMC - LDAP directory
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-01-31 14:07 CET by Jan Christoph Ebersbach
Modified:	2013-02-25 11:31 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
This shows how I selected the object for editing (deleted) 2013-01-31 14:07 CET, Jan Christoph Ebersbach	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jan Christoph Ebersbach

2013-01-31 14:07:18 CET

Created attachment 5029 [details]
This shows how I selected the object for editing

I opened the LDAP directory browser and right-clicked on one of the containers
below the ldap base (without left-clicking it in the first place!).  Than I
selected the Edit operation and expected to see the selected container in the
dialog.  Instead the ldap base (previously selected) object appeared.

For the Edit operation this is very confusing and might cause some trouble. 
For the Delete operation this bug is critical!

Comment 1 Jan Christoph Ebersbach

2013-01-31 14:24:16 CET

This bug was fixed in an errata update, Bug #26062.

Comment 2 Jan Christoph Ebersbach

2013-01-31 14:24:31 CET


*** This bug has been marked as a duplicate of bug 26062 ***