Bug 2004702

Summary:	It appears Multiselect editing of Bugs UI has removed MOST of the fields you could previously edit
Product:	[Community] Bugzilla	Reporter:	Don Bayly <dbayly>
Component:	User Interface	Assignee:	The Bugzilla Team 🤖 <bugbot>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	agk, lmadsen, mschorm
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-15 02:50:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Don Bayly 2021-09-15 18:36:06 UTC

Description of problem: Multiselct Editing of several B Z's at once has removed Most of the fields we use to be able to Modify/change


Version-Release number of selected component (if applicable):


How reproducible:
Select more then 1 BZ to edit.
Press EDIT to change Fields
Attempt to ADD those new BZ's to a any new confidential Group (Just one example of dozens of fields missing)

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jeff Fearn 🐞 2021-09-15 23:04:35 UTC

Group is a product specific fields, that is the values offered are specific to a product. You need to set a product before product specific fields are shown.

The previous form allows selecting invalid combinations, this approach prevents that.

If you set a product are any fields valid for that product missing?

Comment 2 Don Bayly 2021-09-16 15:29:30 UTC

(In reply to Jeff Fearn 🐞 from comment #1)
> Group is a product specific fields, that is the values offered are specific
> to a product. You need to set a product before product specific fields are
> shown.
> 
> The previous form allows selecting invalid combinations, this approach
> prevents that.
> 
> If you set a product are any fields valid for that product missing?

So. The multiedit functionality was  rewritten in its usability. 

I use to be able to just run a query and from that multiselect bzs to group edit.

Was the reason for this change because queries contained multiproduct results and multiedit was assuming something else?

Comment 3 Jeff Fearn 🐞 2021-09-16 22:50:29 UTC

(In reply to Don Bayly from comment #2)
> (In reply to Jeff Fearn 🐞 from comment #1)
> > Group is a product specific fields, that is the values offered are specific
> > to a product. You need to set a product before product specific fields are
> > shown.
> > 
> > The previous form allows selecting invalid combinations, this approach
> > prevents that.
> > 
> > If you set a product are any fields valid for that product missing?
> 
> So. The multiedit functionality was  rewritten in its usability. 
> 
> I use to be able to just run a query and from that multiselect bzs to group
> edit.
> 
> Was the reason for this change because queries contained multiproduct
> results and multiedit was assuming something else?

The old form simply listed all the fields and all the values for all the fields. We had complaints that users had a lot of invalid options offered to them. Adding support for pagination to the old form would have been brutal so we decided to make a new form and while we where at it hide fields and values that would have been rejected and gotten you in to those annoying intermediate pages.

Personally I never saw those intermediate pages because I could cherry pick the right options, but that's something many users had difficulty doing.

One thing you can do is select a product and uncheck the "change this field field" checkbox next to it, this will show you the fields for that product but won't change the product on the bugs.

The new form can be optimized in some ways.

Perhaps if you have selected bugs from the same product then that can be set automatically on the form?

Perhaps if there are bugs from multiple products it could default the product to the first product found and not set the checkbox?

It could get more complicated than that, say show fields available of all the products, but for large numbers of bugs that might get slow to load the form.

Comment 6 Jeff Fearn 🐞 2022-04-07 06:05:55 UTC

*** Bug 2053444 has been marked as a duplicate of this bug. ***

Comment 8 Jeff Fearn 🐞 2022-06-15 02:50:44 UTC

I'm closing this as there are numerous other bugs with specific of things that where missing or broken.