rombert - this is based on a high-level survey of the bug tracker, taking into account bugs with lots of discussion or features which make sense IMO.

• Voting ( 668 )
• New custom field types (14565, 4640, 3790, 6325, 13180 )
• HTML notification emails ( 12830 )
• WYSIWYG/WYSIWYM text editor ( 12744, 12325, 3491, 12915 )
• Case-insensitive searches ( 12145 )
• User groups ( 3444 )
• Edit saved filters ( 3803 )
• E-mail reporting ( 4286, 11195 )
• Hide child issues in filters ( 4617 )
• Allow custom fields for versions, projects, users, notes ( 5278, 6388 )
• Inherited versions ( 5668 )
• Custom fields in workflows ( 5744 )
• Periodic email notifications ( 5887, 6646 )
• Search on specific field ( 7183 )
• Additional authentication types ( 4235 for implementation details )
  • CAS authentication ( 7568 )
  • OpenID authentication ( 8199 )
  • PAM ( 8102 )
  • NTLM ( 3043 )
  • X.509 certificates ( 3303 )
  • NIS ( 4010 )
• Customisable 'my view' page ( 7840 )
• Time planning ( 7945, 10245 )
• Local avatars ( 8257 )
• Per-project tags ( 9716 )
• Assigning multiple persons to an issue ( 5081 )
• Absent users ( 11080 )
• Note snippets/auto-text ( 11131 )
• Diff-style emails ( 985 )
• Better display of attachments ( 12766, 10210 )
• Notifications other than email (e.g. text messages, jabber, etc) ( 10084 )
• Select reporter while adding an issue ( 11615 )

• Refreshed look and feel ( colors, fonts, overall layout ) UI grievances
• Improved interactivity ( in-page dialogs, refresh-less validation, no more using the back button to go back to forms )
  • see also 8899, 15372
  • Client-side charting library, e.g. RaphaelJS, Flot charts
• Better support for Oracle
• Better support for SQL Server
• Better support for DB2
• Track owner of attachments (requires a schema change)
• Should Print pages be dropped in favor of CSS work on View pages?
• SLA support
• User-readable issue keys , e.g. MANTIS-120
• Different issue types ( bug, feature, test ) with different workflows
• Keyboard shortcuts
• Custom dashboards - multiple customisable, shareable, 'my view'-like pages

• Support standard filters like Issues Assigned To Me, Reported By Me, Monitored by Me, etc.
• Creation of custom filters
• Application Token / OAuth Support (rather than username / password)
• More admin APIs
• REST API

• Make jQuery available to extensions.
• Extensions gallery

• Notify admin via web interface when there is a new version of MantisBT available (similar to phpBB).

• Make jQuery available to extensions.
• Drop NuSoap.

— rombert 2013/04/24 12:07 this is IMO something which we justify with features, not something which is a feature candidate

— vboctor - agreed. However, dropping support for certain environments is something that we may need to communicate to the community and get feedback. A survey is one avenue for that. For example, do people care if we require javascipt? drop IE 6 support, etc?

— rombert 2013/04/25 12:00 Agreed, we need to communicate this upfront, for instance 'In order to be able to provide X,Y,Z we will always require Javascript to be enabled/IE 8 or newer etc.

• Require javascript to be enabled.
• Require a modern browser (whatever jQuery requires).
• Require PHP >= 5.3.2 (done in current master)