Bug 30621 - Creating new bug reports seems to fail
Summary: Creating new bug reports seems to fail
Status: RESOLVED WORKSFORME
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Frédéric "LpSolit" Buclin
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-10 16:32 CEST by Marja Van Waes
Modified: 2022-07-12 14:51 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
screenshot showing OP's mistake! (153.78 KB, image/png)
2022-07-12 13:48 CEST, Tony Blackwell
Details

Description Marja Van Waes 2022-07-10 16:32:50 CEST
Tony Blackwell reported this morning that he couldn't file a new bug report.
Aslo https://bugs.mageia.org/buglist.cgi?chfield=%5BBug%20creation%5D&chfieldfrom=24h&list_id=148996 is empty.

https://ml.mageia.org/l/arc/qa-discuss/2022-07/msg00033.html reads:

Hi,
Is there a [problem at bugs.mageia.org?
I've had 2 tries at reporting an apparent bug, get script at end saying thankyou for reporting it - but it doesn't give me a bug number and doesn't add it to my bugs list as its always done.

Ideas?
Tony 

Filing this report to test the issue.
Comment 1 Marja Van Waes 2022-07-10 16:34:28 CEST
Well, this report didn't fail.

Tony, do you mind telling what you did, against which component you tried to file a report and at what time?

Keywords: (none) => NEEDINFO

Comment 2 Frédéric "LpSolit" Buclin 2022-07-12 02:42:16 CEST
(In reply to Marja Van Waes from comment #1)
> Tony, do you mind telling what you did, against which component you tried to
> file a report and at what time?

... and a screenshot if the problem is still present.
Comment 3 Tony Blackwell 2022-07-12 13:45:40 CEST
Duh, My bad everyone.. My apologies, although there is something utterly trivial in lodging the bug which should be fixed.

Late at night, lodged the bug, got a message at bottom of screen saying Thankyou etc.  See attached screen shot.

Real cause: I'd forgotten to put an entry in the Summary as a title.
I looked only at the bottom line of attached screenshot, saying:
That's it.  Thanks very much.....

and completely missed the fact that the cursor had jumped back to the empty Summary field.

Ah well.  Probably the script behind this should be a bit smarter, to offsetfor my stupidity, and not thank me for finishing when essential fields are empty - demostrated in the attached pic.  Guess I'm so used to web forms which won't progress if data is incomplete.

Very grateful for the prompt response from you all.
Regards,
Tony
Comment 4 Tony Blackwell 2022-07-12 13:48:22 CEST
Created attachment 13332 [details]
screenshot showing OP's mistake!

Screenshot showing my error in not completing form at bug submission
Comment 5 Tony Blackwell 2022-07-12 13:53:08 CEST
Could probably fix
a: the wrong messwage at bottom
b: the non-blinking cursor in empty field.  Yes, field is highlighted in yellow but did I scan back up the form when told it was successful....

Please close bug and forget I ever mentioned it.
Regards,
Tony
Comment 6 Frédéric "LpSolit" Buclin 2022-07-12 14:51:21 CEST
(In reply to Tony Blackwell from comment #5)
> Could probably fix
> a: the wrong messwage at bottom

The message at the bottom is hardcoded. It just thanks the user for filling a new bug report, but in no way it is a confirmation message that the bug report has been submitted.


> b: the non-blinking cursor in empty field.  Yes, field is highlighted in
> yellow but did I scan back up the form when told it was successful....

The yellow color only means that the field is mandatory. If you leave this field empty, you should see a popup asking you to write some text in the summary field.


> Please close bug and forget I ever mentioned it.

OK :)

Keywords: NEEDINFO => (none)
Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME


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