Bug 1399101 - 'An unexpected error occurred' when click button 'Remove Selected' directly
Summary: 'An unexpected error occurred' when click button 'Remove Selected' directly
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Extensions
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: 5.0
Assignee: Jeff Fearn 🐞
QA Contact: Jeff Fearn 🐞
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 09:47 UTC by wangjing
Modified: 2018-12-09 06:29 UTC (History)
2 users (show)

Fixed In Version: 5.0.4-rh2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-18 10:15:09 UTC

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

Description wangjing 2016-11-28 09:47:47 UTC 
Description of problem:
'An unexpected error occurred' when click button 'Remove Selected' directly

Version-Release number of selected component (if applicable):
5.0

How reproducible:
always

Steps to Reproduce:
1. preferences->Component Watching page(https://bz-web.host.qe.eng.pek2.redhat.com/userprefs.cgi?tab=component_watch)
2. click button 'Remove Selected' directly without any other operations
3.

Actual results:
after step2: return a page showing:
An unexpected error occurred. This could be a temporary problem, or some code is behaving incorrectly. If this problem persists, please email this page to bugzilla-requests with details of what you were doing at the time this message appeared.
....

Expected results:
no such error, and graceful tips.

Additional info:
Comment 1 Jeff Fearn 🐞 2018-04-11 07:43:24 UTC 
Clicking button without selecting a watch to remove no longer errors.
Comment 2 Jeff Fearn 🐞 2018-04-18 10:15:09 UTC 
This bug has been resolved in Red Hat Bugzilla 5 and can be tested on https://beta-bugzilla.redhat.com

If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.
Note You need to log in before you can comment on or make changes to this bug.