Bug 16 - Make the 'new' link point to the guided new bug form
Summary: Make the 'new' link point to the guided new bug form
Status: RESOLVED FIXED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: unspecified
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: D Morgan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-12 01:13 CET by Samuel Verschelde
Modified: 2011-02-12 23:33 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Samuel Verschelde 2011-02-12 01:13:50 CET
The "new bug" form is very important because it's where every new bug comes from.

It's important to keep it simple, however there are fields that could be useful at this step : 
- RPM Package field
- URL field
- Assign To (the way mandriva's bugzilla works in this regard is interesting : the assign to field is updated according to the RPM name, using the maintainer's db maybe)
- CC field (to add a friend in CC directly during bug creation rather than needing to add them after bug creation) ?

I'm not sure about the last two, but quite sure about RPM and URL fields, provided their meaning is explained on the page.
Comment 1 D Morgan 2011-02-12 10:08:38 CET
have you tried  http://bugs.mageia.org/enter_bug.cgi?product=Mageia&format=guided ?
Comment 2 D Morgan 2011-02-12 10:09:13 CET
btw i need to fix the "New" button to point to http://bugs.mageia.org/enter_bug.cgi?product=Mageia&format=guided
Comment 3 Samuel Verschelde 2011-02-12 10:32:29 CET
Indeed I hadn't seen the guided form, because I used the "new" button.

Changing the bug short description to "Make the 'new' link point to the guided new bug form"

Summary: Improve "new bug" form => Make the 'new' link point to the guided new bug form

Comment 4 D Morgan 2011-02-12 12:03:07 CET
fixed in svn, and in production

Status: NEW => RESOLVED
Resolution: (none) => FIXED

D Morgan 2011-02-12 23:33:53 CET

Priority: --- => Normal


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