If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

The 'bug number' is invalid. If you are trying to use QuickSearch, you need to enable JavaScript in your browser. To help us fix this limitation, add your comments to bug 70907

RESOLVED WORKSFORME

Status

()

Bugzilla
Creating/Changing Bugs
--
major
RESOLVED WORKSFORME
11 years ago
11 years ago

People

(Reporter: dchandrashaker, Unassigned)

Tracking

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Build Identifier: 2.18rc1 

After creating products and subcomponents, we want to submit a bug, after duly filling all the required fields, when we commit the bug to db iam getting error like "The 'bug number' is invalid. If you are trying to use QuickSearch, you need to enable JavaScript in your browser. To help us fix this limitation, add your comments to bug 70907"  we have just installed the database bugs, by successfully running the ./checksetup.pl,  there r no issues when iam creating database, apache + perl setup is fine

Reproducible: Always

Steps to Reproduce:
1.Login as any valid user who has permissions to submit a bug
2.go to NEW  to submit the bug
3.Select version, select component, priority , give emailid:- assign to, copy the url of the bug, write summary, give descpription, fill depends on, blocks, and press commit button , u will get error  "The 'bug number' is invalid. If you are trying to use QuickSearch, you need to enable JavaScript in your browser. To help us fix this limitation, add your comments to bug 70907" 


Expected Results:  
it should submit the bug and come to mainpage

Comment 1

11 years ago
1. Try another web browser
2. Verify the blocks/depends on fields are empty
3. Try form get from jesse's bookmarklets site

Comment 2

11 years ago
You are using a very old version of Bugzilla (2.18 RC1). Upgrade to 2.18.6 first or install Bugzilla 3.0 RC1 and try again. This error message has been fixed a long time ago.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.