Closed
Bug 163457
Opened 23 years ago
Closed 23 years ago
bugs not registered as "new"
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: mozilla, Assigned: gerv)
References
Details
Attachments
(1 file)
|
1.13 KB,
patch
|
timeless
:
review+
bbaetz
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.1) Gecko/20020814 MultiZilla/v1.1.20
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.1) Gecko/20020814 MultiZilla/v1.1.20
I've been given the authorization to register bugs as "new"
when using the helper form they get registered as "unconfirmed"
in the old version my bugs started as "new"
If using the enter bug form, my bugs can start as "new"
Reproducible: Always
Steps to Reproduce:
Comment 1•23 years ago
|
||
-> bugzilla helper, but ISTR that gerv did that on purpose
Assignee: justdave → gerv
Component: Administration → Bugzilla Helper
Product: Bugzilla → Webtools
Version: unspecified → other
| Reporter | ||
Comment 2•23 years ago
|
||
seems to be a problem only when I report bugs for the browser
this bug did start as "new"
| Assignee | ||
Comment 3•23 years ago
|
||
I didn't do this on purpose, and he is absolutely right. I wonder why this is.
I'll try and work it out.
Gerv
| Assignee | ||
Comment 4•23 years ago
|
||
This problem is due to some convoluted logic in post_bug, which gets it wrong
when bug_status is absent completely. Rather than add bug_status to the new
template, I've fixed the logic in post_bug instead.
Gerv
| Assignee | ||
Comment 5•23 years ago
|
||
-> me, Bugzilla product.
Comment on attachment 95891 [details] [diff] [review]
Patch v.1
yeah this bit me once, someone decided to triage my &format=simple filed bug.
however i like being able to file unconfirmed bugs, although i'm not certain
i'd ever use that option in simple mode. Ok, conclusion: if i want to file an
unconfirmed bug, i'll use advanced mode.
for reference, the old logic was:
if there's a status, and if it's unconfirmed or the user can't edit/confirm
then remove the flag. when there's no flag, it's unconfirmed.
the new logic is, if the user can edit[/confirm] then use the provided status
or mark it as new.
r=timeless
Attachment #95891 -
Flags: review+
Comment 7•23 years ago
|
||
Comment on attachment 95891 [details] [diff] [review]
Patch v.1
Use ||= for the $::FORM{'bug_status'}. I don't think that any of the carefully
aranged logic is broke by this, but you probably want to keep some of the
comment.
r=bbaetz
Attachment #95891 -
Flags: review+
| Assignee | ||
Comment 8•23 years ago
|
||
Fixed.
Checking in post_bug.cgi;
/cvsroot/mozilla/webtools/bugzilla/post_bug.cgi,v <-- post_bug.cgi
new revision: 1.61; previous revision: 1.60
done
Gerv
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 9•23 years ago
|
||
*** Bug 164460 has been marked as a duplicate of this bug. ***
Updated•13 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•