Closed Bug 1453605 Opened 8 years ago Closed 7 years ago

status and tracking flags can't be set when bug gets created because dropdowns are disabled

Categories

(bugzilla.mozilla.org :: Bug Creation/Editing, defect)

Production
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: aryx, Unassigned)

References

Details

Status and tracking flags can't be set when a bug gets created because the dropdowns are disabled. 1. Go to https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox 2. Click on the "Set bug flags" button. Actual result: "Tracking" and "status" flag dropdowns are disabled. Expected result: Dropdowns not disabled. Modifying them after one has submitted the bug works.
I had reproduced the issue in two profiles and for different BMO products (Firefox, Firefox Build System). But when I filed bug 1453607, the issue was gone. Had filed bug 1453607 before when the issue still applied.
This issue hit again this week, this time in :nataliaCs' profile.
(In reply to Sebastian Hengst [:aryx][:archaeopteryx] (needinfo on intermittent or backout) from comment #2) > This issue hit again this week, this time in :nataliaCs' profile. Is this for a particular tracking and status flag, or all of them? Asking because they can be configured to be editiabe or not on entry.
Flags: needinfo?(aryx.bugmail)
All of them (the whole block on the left, the block on the right with needinfo etc. is unaffected and enabled).
Flags: needinfo?(aryx.bugmail)
Looks like the flag dropdown lists are disabled until a component is selected. I’m not sure if it’s really a necessary step. Do flags depend on components?
(In reply to Kohei Yoshino [:kohei] from comment #5) > Looks like the flag dropdown lists are disabled until a component is > selected. I’m not sure if it’s really a necessary step. Do flags depend on > components? Yes
In that case, this bug is probably WORKSFORME. The UX could be improved though.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
See Also: → 1541204
You need to log in before you can comment on or make changes to this bug.