Remove hard-coded references to core::untriaged

NEW
Unassigned

Status

()

task
6 months ago
2 months ago

People

(Reporter: emceeaich, Unassigned)

Tracking

(Blocks 1 bug)

Staging
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

What should the current hard coded value become? General?
Flags: needinfo?(ehumphries)
Let's look at the places that's hard coded. I'm assuming its in the bug 'wizard' flow? Product engineering may want to have something to say here.
Flags: needinfo?(ehumphries)
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞‍♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #2)
> Let's look at the places that's hard coded. I'm assuming its in the bug
> 'wizard' flow? Product engineering may want to have something to say here.

Yes it is the Guided form I am mostly concerned with. If the user doesn't manually select a component it will choose Untriaged for them and if we remove it it will throw an error.

dkl
Flags: needinfo?(ehumphries)
Okay, I've created a couple of related bugs to get to a solution.
Flags: needinfo?(ehumphries)
Type: enhancement → task
You need to log in before you can comment on or make changes to this bug.