1151745 - add ui to minimise steps required to move bugs between products

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: User Interface, defect)

Description

[:glob ✱]

add ui to minimise steps required to move bugs between products, using the component search mechanism and smart field mapping.

Comment 1

[Mike Hoye [:mhoye]]

Thanks, I was just about to file this!

Comment 3

[:glob ✱]

Attachment: 1151745_1.patch

- update component, version, milestone, and groups when product changed
- bring product/component searching onto show_bug
- skip confirmation page when new values are valid

Comment 4

[David Lawrence [:dkl]]

Comment on attachment 8595748 [details] [diff] [review]
1151745_1.patch

Review of attachment 8595748 [details] [diff] [review]:
-----------------------------------------------------------------

Nits:
- When performing search and selecting same product, the component and other affected fields are highlighted. Only highlight if product is different.
- When selecting a new product and going back to old, it has the affected fields highlighted. Ideally, all highlighted fields should go back to normal.
- Note: The above changes are not worth it if it adds a lot of additional complexity.

Fix on Commits:
- Remove extensions/BugModal/template/en/default/bug_modal/groups_new_product.html.tmpl

All else works and looks good. r=dkl

::: extensions/BugModal/lib/WebService.pm
@@ +278,5 @@
> +    }
> +
> +    my $default_group_name = $product->default_security_group;
> +    if (my $default_group = first_value { $_->{group}->name eq $default_group_name } @groups) {
> +        # beacuse we always allow the default product group to be selected, it's never invalid

because

Comment 5

[:glob ✱]

To ssh://[e-mail]/webtools/bmo/bugzilla.git
   0d15453..dac9873  master -> master

Comment 6

[Mark Côté [:mcote]]

This is now live. \o/

Comment 7

[fireattack [:fireattack]]

(In reply to Mark Côté [:mcote] from comment #6)
> This is now live. \o/

Is it live?

Because I still need two steps to change the component of a bug. When I changed the bug's Product from Firefox to Core, its component list didn't update and I can't directly choose the component I want untile I hit "save changes".

By the way, why the hell we can't submit bug for "Core" directly? It affects workflow a lot I'd say.

Comment 8

[fireattack [:fireattack]]

(In reply to Mark Côté [:mcote] from comment #6)
> This is now live. \o/

Is it live?

Because I still need two steps to change the component of a bug. When I changed the bug's Product from Firefox to Core, its component list didn't update and I can't directly choose the component I want untile I hit "save changes".

Comment 9

[:Gijs (out for now; he/him)]

(In reply to Benjamin Peng from comment #8)
> (In reply to Mark Côté [:mcote] from comment #6)
> > This is now live. \o/
> 
> Is it live?
> 
> Because I still need two steps to change the component of a bug. When I
> changed the bug's Product from Firefox to Core, its component list didn't
> update and I can't directly choose the component I want untile I hit "save
> changes".

This is only working if you have the "Use experimental user interface" pref enabled.

Comment 10

[:glob ✱]

(In reply to Benjamin Peng from comment #7)
> By the way, why the hell we can't submit bug for "Core" directly? It affects
> workflow a lot I'd say.

you can - choose 'other products' then 'core', or use the 'find product' field to search for the component.
you could also 'switch to the advanced bug entry form' which shows 'core' on the initial product list.