Issue 18498 - AcceptAll is ambiguous in "Accept or Reject Changes" dialog when multi-rows selected
Summary: AcceptAll is ambiguous in "Accept or Reject Changes" dialog when multi-rows s...
Status: UNCONFIRMED
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: 638
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-21 17:35 UTC by eakle
Modified: 2013-02-07 22:32 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description eakle 2003-08-21 17:35:06 UTC 
Select menuitem Edit-->Changes-->Accept or Reject... and see the Accept or 
Reject Changes dialog.  This showed about 100 changes in the list.  I multi-
selected a large group of these (all the ones made today) and then 
instinctively (and in error) pressed the "Accept All" button.  And, of course, 
it processed all the changes in the list, not just the ones I had selected.

Suggestion: Accept All does not have a clear meaning when multiple-rows are 
selected.  If multiple rows are selected and user presses Accept All, then I 
suggest that the system should ask the user what they want to do: just process 
the selected rows, or process all rows.
Comment 1 jack.warchold 2003-12-08 13:35:35 UTC 
this would more be an enhancement then a defect.

i think the current behaviour is the correct one. but it would be more user 
friendly to ask the user, if more then one recorded entry is selected and they 
press the accept all button, what they really intented to do.

changed issuetype to enhancement
reassigned to the owner of enhancement issues
Comment 2 stp 2005-08-14 21:10:20 UTC 
thing->liz: Maybe one you should see. If not, sorry.
Comment 3 bettina.haberer 2010-05-21 14:45:09 UTC 
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".