Confirm
241
edits
Changes
→Defining Roles in BMO
** Admins normally need even higher groups for editing users, products, etc.
* Could also based on statistics, how many patches the user has committed, reviewed, etc. How many bugs the user has closed that were not their own.
* We could come up with an entirely new storage format for defining roles using a BMO extension and custom tables. Then manually (or in an automated way) figure out who woulwould go into which role. BMO could then use that data to change the UI and make other suggestions when viewing a bug report based on the role.
* With custom tables, users could take on more than one role.
** Also can switch between them. Could use stats to suggest roles.
* Simpler route would be to just provide a drop down on the show bug page that would switch the views from for example, 'standard' to 'triage', and then remember the selection for the next page load.
** This could be done for the first iteration and then refined for more roles later. Triage should be our first goal.
* Determine using feedback from the different groups what changes need to be done for the page based on role selected.
** Hide/display certain fields
** Provide shortcut links to perform common tasks (Next Actions (tm)).
=== BMO Tool Enhancements Per User Role ===
