BMO/42Upgrade/Postpone: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "Subject: [ANNOUNCEMENT] BMO Bugzilla 4.2 Upgrade Testing [UPDATE] Greetings, The Mozilla Bugzilla team is announcing that unfortunately the rollout of Bugzilla 4.2 has been pos...")
 
No edit summary
 
Line 6: Line 6:


Due to some great feedback recieved during the initial testing of 4.2, some issues were found that will take some additional time to investigate and implement appropriate fixes before rolling out the new version to production. Your feedback is very valuable and continues to help in delivering a solid release.
Due to some great feedback recieved during the initial testing of 4.2, some issues were found that will take some additional time to investigate and implement appropriate fixes before rolling out the new version to production. Your feedback is very valuable and continues to help in delivering a solid release.
One of the issues was related to advanced search functionality changes in 4.2. Further details will be
forthcoming, and there will be time to test the new search functionality before it is rolled out


For more detailed project information as well as the full schedule, see:
For more detailed project information as well as the full schedule, see:
Line 24: Line 27:
for general delivery so feel free to also use the test BzAPI to make bug
for general delivery so feel free to also use the test BzAPI to make bug
changes and other write operations.
changes and other write operations.
Note: The code on the backend supporting search has changed significantly from 4.0 and special attention should be given to verify your saved searches still produce the expected results. As part of the sanitization process of the data for testing, saved searches are removed from the database. This is in case there is any sensitive data contained in the searches that someone may see when requesting a copy of the database.
As a workaround to test your saved searches on the 4.2 system:
1. Go to https://bugzilla.mozilla.org.
2. Run your saved search as you normally would which pulls up the
complete bug list.
3. Click 'Edit Search' at the bottom of the buglist page.
4. When on the query builder page, change the hostname in the address field from bugzilla.mozilla.org to bugzilla.allizom.org and reload the
query page.
5. Click 'Search' which will bring up a new bug list.
6. You should get similar results in both places although private bugs will be absent on the 4.2 test system.


Please file any bug reports in the production Bugzilla system at https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&version=Development%2FStaging
Please file any bug reports in the production Bugzilla system at https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&version=Development%2FStaging
Confirmed users
241

edits

Navigation menu