« Bugzilla Issues Index
#212 — no VERIFIED state for bugs?
- bug_id:
212
- creation_ts:
2011-10-04 20:27:00 -0700
- short_desc:
no VERIFIED state for bugs?
- delta_ts:
2013-05-09 13:40:25 -0700
- product:
TC39 Infrastructure
- component:
bugzilla
- version:
unspecified
- rep_platform:
All
- op_sys:
All
- bug_status:
CONFIRMED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
Michael Dyck
- assigned_to:
Dave Herman
- cc:
trbaker
- commentid:
495
- comment_count:
0
- who:
Michael Dyck
- bug_when:
2011-10-04 20:27:28 -0700
When a new draft of the ES spec comes out, I check whether it fixes bugs I've submitted in the "Draft for 6th Edition" product. When I find it has, I've been setting the status to CONFIRMED, but I've just realized that that means something else, and I should instead be using VERIFIED. However, there doesn't appear to be a VERIFIED status in this Bugzilla instance.
Is that intentional? If so, what should I do?
- commentid:
3721
- comment_count:
1
- who:
Trevor Baker
- bug_when:
2013-05-09 07:43:49 -0700
I suggest you use RESOLVED->FIXED for this.
- commentid:
3722
- comment_count:
2
- who:
Trevor Baker
- bug_when:
2013-05-09 07:51:35 -0700
MInd you, it is strange that there are 5 "status" options in the search interface and only 4 on the bug edit screen. VERIFIED is indeed missing.
- commentid:
3723
- comment_count:
3
- who:
Michael Dyck
- bug_when:
2013-05-09 13:40:25 -0700
(In reply to comment #1)
> I suggest you use RESOLVED->FIXED for this.
No, that's what the assignee uses to indicate that he believes he's fixed the bug.