Bug 188394 - easy enter bug appears to have disappeared
Summary: easy enter bug appears to have disappeared
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 2.18
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-08 23:36 UTC by Alex Lancaster
Modified: 2007-04-18 17:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-11-17 00:14:53 UTC
Embargoed:


Attachments (Terms of Use)

Description Alex Lancaster 2006-04-08 23:36:58 UTC
Description of problem:
The "Easy Enter" (non-expert) bug entry appears to have gone:

https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi

Returns "404 Not Found"

Also can't find any other link on http://bugzilla.redhat.com that provides
similar functionality.

Comment 1 Alex Lancaster 2006-05-04 07:54:04 UTC
Ping?  It's been almost a month and the easy enter bug entry has not returned,
nor has there been a response on this bug.

Comment 2 Alex Lancaster 2006-06-02 00:45:38 UTC
It appears that:

https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi

is now back, but there is no way to find it from the main bugzilla entry points.

For example, there is no link to it from either the "expert" form:

https://bugzilla.redhat.com/bugzilla/enter_bug.cgi

(however the "easy" version does link back to the "expert" version)

or from the main "New" link at the top of the page, nor any link from the main
bugzilla home page:

https://bugzilla.redhat.com/bugzilla/index.cgi

so it's unlikely that newbies (who are the primary target would be able to find
this).

Comment 3 Alex Lancaster 2006-07-11 22:51:43 UTC
Ping?  Easy enter bug is still not linked from anywhere.

Comment 4 Alex Lancaster 2006-11-17 00:14:53 UTC
Looks like it is now linked on the "New" page, but seems to have some problems
loading.  Since the original report is now fixed, closing this bug.


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