MantisBT 1.3.0-rc.2 Released

This second and last 1.3.x release candidate has 127 bug fixes and improvements.  Some of the highlights include:

  • @ mentions support – mention other users in issue summary, description and notes and they will get an email alerting them to the fact that they were mentioned with the appropriate context.
  • Support for avatar plugins – We still ship Gravatar out of the box, but it is now very easy to implement other avatar providers that can be based on file system or LDAP.
  • Support for user lifecycle plugin events – Added plugin events the handle and extend user lifecycle events (see extensibility section below)
  • Allow administrators to impersonate users – Administrators can now impersonate a user account to verify that it’s access level is as expected or to troubleshoot issues that their users are having with Mantis.
  • Support for notes and tags as columns to configure for view issues, print issues, csv/excel export
  • Support for login using email address – Users can login using either usernames or email addresses.
  • Enforcing email uniqueness – User emails must be unique or empty for service accounts.
  • Enable configuration for email notifications for category owner – The same way it is possible to configure whether reporter of an issue should receive notifications, the same can now happen for category owners.
  • Re-implemented parsing of complex configuration types for Configuration Report – Re-implemented parsing logic in a robust way leveraging standard PHP methods designed to parse PHP expressions.
  • Tagging directly from report issue page – You no longer have to report an issue, then go and tag it, this can now be done in a single step.

Checkout the new release on mantisbt website and report any issues you may find via our official bugtracker.

This entry was posted in MantisBT and tagged . Bookmark the permalink.

3 Responses to MantisBT 1.3.0-rc.2 Released

  1. Werner Karl says:

    email uniqueness

    Has this been discussed with your user base? If yes, where? Is there a description how you intend to do that? Will it be configurable?

    Do you really want to enforce email uniqueness? This is a show stopper for us! We definitely need different users with identical email address.

    • vboctor says:

      Email uniqueness is configurable. You can turn it off as follows:

      $g_email_ensure_unique = OFF;

  2. rakekniven says:

    Hello mantisbt crew,

    thanks for keeping progress towards version 1.3
    Gave rc2 already a try and no problems so far.

Comments are closed.