If the assignee field has something other than the default in it, it should be assumable that the bug is assigned to someone, so an ASSIGNED status is redundant. INPROGRESS can indicate that someone has started work on the bug and adds new information, and is apparently the way some (or more?) people have been using ASSIGNED anyway
Yes, this would make more sense to me, and I've actually thought about changing the Bugzilla default to be that. Might want to make it IN_PROGRESS.
Severity: normal → enhancement
I'd prefer the straight INPROGRESS, personally, if only because on buglists it'll get cut to four letters and would be INPR instead of IN_P.
Yeah. The other direction to take would be to just eliminate this state, and have people use the whiteboard (keyword, flag, whatever) to indicate that they're actually working on it... I'm not sure how many people actually use the ASSIGNED state. [But it's mostly harmless to have INPROGRESS, so either way is fine.]
This has been done as part of the upstream workflow changes (well, it's IN_PROGRESS) and we hope to have those on b.m.o. before too long. Gerv
Component: Bugzilla: Other b.m.o Issues → Bugzilla: Keywords & Components
QA Contact: other-bmo-issues → timeless
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
while renaming ASSIGNED to IN_PROGRESS is a great idea, it isn't something that we can entertain on BMO. the list of statuses is now considered a 'static api' as any changes to them would cause significant breakage of systems which interact with bugzilla.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
QA Contact: timeless
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.