User talk:LpSolit

Bugzilla 3.2 Roadmap

We are getting close to the feature freeze date for Bugzilla 3.0. The trunk will remain frozen for several weeks, till Bugzilla 3.0 RC1 is released. Then it will open again for Bugzilla 3.2. Wow, I never expected to mention 3.2 as being part of the near future. But how will Bugzilla 3.2 look like? Which features should it have that didn't go into 3.0? Probably tasks from the 3.0 roadmap which didn't land on time, but what else?

Here are a few thoughts:

• Communication between Bugzilla installations.
• Ability to share reports among users (similar to shared saved searches).
• Light UI for the navigation from a mobile phone (requires small pages in size too due to limited memory capacity).
• Improve the charting system.
• Improve table and graph reports (ability to specify a lower and upper limits; ability to sort results).
• Code cleanup: All Bugzilla::* should use Bugzilla::Object to create and update objects. And all .cgi should use these Bugzilla::* objects instead of doing SQL queries themselves.
• process_bug.cgi must use Bugzilla::Bug::update().
• Implement additional custom fields.
• Offer an easy way to implement plugins.
• Make the UI more intuitive (require less clicks, add more links to help files or common tasks, ...).
• Better management of branches (currently, Bugzilla has no idea what a branch is).
• Add a UI to edit custom rules about bug creation and editing (a UI for Bug::check_can_change_field()).