Red Hat Bugzilla – Bug 474791
Adding new Boolean Chart doesn't work as expected
Last modified: 2013-06-23 22:12:47 EDT
Steps to Reproduce:
1. Go to Advanced query
2. Click "Add Another Boolean Query"
3. Add another Boolean Query under the first by clicking "Add Another Boolean Query" again (the same button as pushed before, not the button under the second query)
Page refreshes but there is no new boolean query. Nothing changed. Not below the first or the second existing boolean query.
A new boolean query would be added below the first and thus, what was the second boolean query would be made the third.
-OR- if for some reason this is undesirable for some technical reason, then a new boolean would be added below the last boolean (not good, because then the order isn't preserved)
-OR- an error notice is provided stating WHY the new boolean couldn't be added.
Or, i guess, remove all the 'add new boolean query' buttons that aren't going to work so we don't expect them to be functional.
This bug has aready been reported upstream. We can work on this issue ourselves if time/resources allow.
IMO, the "Add another boolean chart" for all charts except for the last in the list should changed to "Remove this boolean chart". Also buttons for the AND/OR lines should be added to remove just those as well.
*** Bug 472041 has been marked as a duplicate of this bug. ***
Still valid since most recent upgrade to 3.6
Just load up BZ advanced query. Put first bool query. Then hit add new bool query. Then fill in those details. then hit the add new bool query underneith the first query again and the page will simply refresh without changing anything. It should, rather, bump the second query to be the third and add a new empty query as second.
This bug is still valid in 4.2; super frustrating user experience. In fact, the 4.2 is even worse since now i can't use my browsers back button to 'undo'.
I start to build a query... then i have to start from scratch if i realize the ordering is wrong.
This will not be fixed in Red Hat Bugzilla. If you want it addressed, we suggest you log a bug with upstream Bugzilla ( https://bugzilla.mozilla.org/ )