1469782 - Cannot change component of multiple bugs if list contains bugs in multi products but all checked bugs are in the same product

Status: NEW

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

Description

[Benjamin Bouvier [:bbouvier] (inactive)]

I'd like to change the component of a few bugs after doing a large search, to set them to a newly created component. However, in the select dropdown in front of Component, I only get the default option which reads something like "-- select here --".

I tried to select the "Core" product first, because I think the correct way to change component is first to select a product, and then the component list gets reloaded, whenever I need to change component for a single bug. However, it didn't work here.

Am I missing something here?

Comment 1

[Kohei Yoshino]

I think you are talking about the "Change Several Bugs at Once" page. Looks like, if the bugs are under multiple products, the Component dropdown shows no options except for "--do_not_change--", but when clicking the Commit button, the "Verify Version, Component, Target Milestone" appears where you can choose a component. It's a poor UX but the change can still be made, apparently.

Comment 2

[Benjamin Bouvier [:bbouvier] (inactive)]

> I think you are talking about the "Change Several Bugs at Once" page.

That is correct. Sorry if I've put this bug under the wrong component.

> Looks like, if the bugs are under multiple products, the Component dropdown shows no options except for "--do_not_change--", but when clicking the Commit button, the "Verify Version, Component, Target Milestone" appears where you can choose a component. It's a poor UX but the change can still be made, apparently.

Do you say that I need to click "commit", then very quickly change the Component before the commit confirmation page shows up?

Comment 3

[Kohei Yoshino]

Attachment: Screenshot of Verify Version, Component, Target Milestone page

Sorry, I meant: after clicking the Commit button, the "Verify Version, Component, Target Milestone" *page* appears, like this screenshot. You can (actually, you have to) choose a component on that transitional page, then click the Commit button again to complete the change.

Comment 4

[Kohei Yoshino]

So, basically, the UI should be changed like this;

1. The Component dropdown list should be disabled and instead say "Choose a new component on the next page"
2. The same applies to the Version and Target Milestone dropdown lists
3. The "Commit" button should say "Next" instead

Comment 5

[Benjamin Bouvier [:bbouvier] (inactive)]

(In reply to Kohei Yoshino [:kohei] from comment #3)
> Created attachment 8986403 [details]
> Screenshot of Verify Version, Component, Target Milestone page
> 
> Sorry, I meant: after clicking the Commit button, the "Verify Version,
> Component, Target Milestone" *page* appears, like this screenshot. You can
> (actually, you have to) choose a component on that transitional page, then
> click the Commit button again to complete the change.

Interesting. In my case, all the bugs were already in the "Core" product, so trying to change the Product didn't trigger the transitional page and I directly got to the confirmation page. So there was no way to change the component at all. Apart maybe from changing the component to another one temporarily, just to trigger the transitional page (but that would be inconsiderate for all the people in both components who would get spammed a lot :)).

Comment 6

[Kohei Yoshino]

Um, yes, interesting. My guess is, your list had bugs in multiple products but you only checked Core bugs? In that case, based on my local test, the change will be made immediately, and there’s no way to change the component…

Comment 7

[Benjamin Bouvier [:bbouvier] (inactive)]

Yes, sounds like it indeed.

Comment 8

[Kohei Yoshino]

Then the solution is more complicated than Comment 4. The Component, Version and Target Milestone dropdown lists have to be updated dynamically depending on checked bugs.

Comment 9

[Benjamin Bouvier [:bbouvier] (inactive)]

Ping, is there any progress or planning on this? We'd like to mass-change components for WebAssembly bugs, and this is preventing us to do so.

Comment 10

[Kohei Yoshino]

:erahm just encountered this bug. I’ll figure out if I can fix this easily, otherwise we have to wait for a complete overhaul in Bug 1531859.

Comment 11

[Eric Rahm [:erahm]]

(In reply to Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat) from comment #10)

:erahm just encountered this bug. I’ll figure out if I can fix this easily, otherwise we have to wait for a complete overhaul in Bug 1531859.

No rush from my side, this is the first time I've run into the issue and it probably took me 30 minutes or so to figure out what was going on and just do everything manually. It was probably more annoying for the people watching the components involved getting a steady trickle of notifications though.

Comment 12

[Kohei Yoshino]

Can solve this in the frontend.

Comment 13

[Kohei Yoshino]

Attachment: GitHub Pull Request

Comment 14

[Benjamin Bouvier [:bbouvier] (inactive)]

Thanks for fixing this! I had given up moving bugs to the WebAssembly component because of this particular issue.

Comment 15

[Falguni Islam]

Hello, I am new to contributing to Bugzilla can you assigned me to this issue so that I can learn to fix these bugs and also suggest to me how can Is start working on this bug to fix it.