canmove, Confirmed users
1,126
edits
BMO/Requesting Changes: Difference between revisions
→Changes: Explain suggested reviewers and link to report
(→Changes: Explain suggested reviewers and link to report) |
|||
| Line 105: | Line 105: | ||
===Changing Product, Component, Version or Milestone Name=== | ===Changing Product, Component, Version or Milestone Name=== | ||
Bugzilla uses integer mappings internally for mapping IDs to human readable names such as Product, Component, etc. But when creating store queries in the form of a URL or when specifying a product to file a bug against, it doesn't use the ID, it uses the name. When a textual name is changed in BMO using the admin UI to something else, Bugzilla continues to work properly as it still uses the same ID everywhere internally and in the database. But if a stored query or a URL has been passed around to others via a wiki page, mailing list, etc. then the URL will no longer be valid. Users will need to update their queries and revise and relevant documentation to reflect the name change. Bugzilla, and BMO for that matter, does not support aliasing of the new name to any old names so that the old queries will continue to work. BMO admins will try | Bugzilla uses integer mappings internally for mapping IDs to human readable names such as Product, Component, etc. But when creating store queries in the form of a URL or when specifying a product to file a bug against, it doesn't use the ID, it uses the name. When a textual name is changed in BMO using the admin UI to something else, Bugzilla continues to work properly as it still uses the same ID everywhere internally and in the database. But if a stored query or a URL has been passed around to others via a wiki page, mailing list, etc. then the URL will no longer be valid. Users will need to update their queries and revise and relevant documentation to reflect the name change. Bugzilla, and BMO for that matter, does not support aliasing of the new name to any old names so that the old queries will continue to work. BMO admins will try harder to remind requesters that these issues may arise when making these types of name changes. | ||
Note that this also affects BzAPI or the newer native REST API in that you will need to update the search parameters for bug searches to reflect the name changes as well. | Note that this also affects BzAPI or the newer native REST API in that you will need to update the search parameters for bug searches to reflect the name changes as well. | ||
===Suggested Reviewers=== | |||
A curated list of users can be suggested when the review flag is set for a patch, to aid new contributors in picking a reviewer. These suggested reviewers can be set globally for a product, or on a per-component basis. For the current list of users, see the [https://bugzilla.mozilla.org/page.cgi?id=review_suggestions.html suggested reviewers report]. | |||
===Usernames and Passwords=== | ===Usernames and Passwords=== | ||