MantisBT 2.13.1 and 2.12.2 released

In order to stay up to date with the latest MantisBT news and participate in our polls, please follow us on twitter and retweet to spread the word!

Starting with MantisBT 2.13.0 the PHP mbstring extension is mandatory. Ensure that it is enabled on your server, or ask your provider if you are not the administrator of the server.

MantisBT 2.13.1

Maintenance release for 2.13.x series.

  • 0024202[markdown] Broken rendering of @ mentions, # issue and ~ note links (atrol)

MantisBT 2.12.2

Maintenance release for 2.12.x series.

  • 0024201[markdown] Broken rendering of @ mentions, # issue and ~ note links (atrol)

MantisBT 2.13.0

A feature release including functional improvements and bug fixes.

  • 0016070[email] Delay due to Mantis trying sending emails to non existent address (vboctor)
  • 0023498[filters] Filtering “note by” with “none” does not return any result (cproensa)
  • 0007264[filters] Not able to filter issues that have no relationship assigned (cproensa)
  •  0008167[filters] Filter settings saved when using Anonymous account (cproensa)
  •  0008204[filters] Filters not remembered when clicking through from “My View” (cproensa)
  • 0022785[api rest] Support adding attachments when reporting issues (vboctor)
  • 0023214[performance] Remove usage of outdated phputf8 library (atrol)
  • 0023998[code cleanup] Implement IssueAddCommand and use it from SOAP, REST and Web UI (vboctor)
  • 0023999[code cleanup] Implement IssueDeleteCommand and use it from SOAP, REST, and Web UI (vboctor)
  • 0024000[api rest] Add Issue REST API doesn’t trigger EVENT_REPORT_BUG_DATA plugin event (vboctor)
  • 0024001[api soap] Add Issue SOAP API doesn’t trigger EVENT_REPORT_BUG_DATA plugin event (vboctor)
  • 0024002[api rest] Add Issue REST API doesn’t trigger issue_create_validate custom function (vboctor)
  • 0024003[api soap] Add Issue SOAP API doesn’t trigger issue_create_validate custom function (vboctor)
  • 0024004[api rest] Add Issue REST API doesn’t trigger issue_create_notify custom function (vboctor)
  • 0024005[api soap] Add Issue SOAP API doesn’t trigger issue_create_notify custom function (vboctor)
  • 0024006[api rest] Add Issue REST API doesn’t trigger EVENT_REPORT_BUG plugin event (vboctor)
  • 0024007[api soap] Add Issue SOAP API doesn’t trigger EVENT_REPORT_BUG plugin event (vboctor)
  • 0024008[api rest] Add Issue REST API doesn’t add the issue to recent list (vboctor)
  • 0024009[api soap] Add Issue SOAP API doesn’t add the issue to recent list (vboctor)
  • 0010853[filters] In View Issues list, several columns are sorted by Id instead of display value (cproensa)
  • 0013177[filters] On ‘View Issues’ Page the filter does not allow user to select ‘blank’ (‘No Category’) Category (cproensa)
  • 0021865[filters] Filter out duplicated issues (cproensa)
  • 0021867[filters] Filter filed “relationships” resets its value when “duplicate of” is selected (cproensa)
  • 0023476[bugtracker] Can’t login if admin directory has restricted access (atrol)
  • 0023499[filters] Filtering with “note by” shows results from private notes for unprivileged users (cproensa)
  • 0023500[filters] Search filter returns matches in private notes for unprivileged users (cproensa)
  • 0023501[filters] Filter “monitored by” does not have option for “none” (cproensa)
  • 0023502[filters] Filter “assigned to” does not account for configuration “view_handler_threshold” (cproensa)
  • 0023504[filters] Filter “monitored by” does not account for configuration “show_monitor_list_threshold” (cproensa)
  • 0023506[filters] Filter tags inconsitent with OR filter operator (cproensa)
  • 0023538[filters] Filter field for relationship bug id is set to -1 by default (cproensa)
  • 0023549[db mysql] Entering Emojis in comments with a user mention crashes with an error (atrol)
  • 0024042[filters] filter on relationships mistuned by switching sort order (cproensa)
  • 0024056[custom fields] Custom Fields of type “Textarea” cannot contain more than 255 chars due to bug_history table (atrol)
  • 0024089[authentication] POST request to login_password_page.php return 405 when admin folder is deleted or access restricted (atrol)
  • 0024128[administration] Unable to start system check or installation with wrong PHP version (atrol)
  • 0024140[filters] Application error 401: “ORDER BY clause is not in SELECT list” when sorting by category or project (cproensa)
  • 0022376[documentation] Wrong documentation of string customization (atrol)
  • 0023161[timeline] Show File Attachment events in Timeline (dregad)
  • 0024158[bugtracker] Support providing a default value for issue description (vboctor)
  • 0024159[documentation] $g_default_bug_steps_to_reproduce not documented (vboctor)
  • 0024160[documentation] $g_default_bug_additional_info not documented (vboctor)

MantisBT 2.12.1

Maintenance release for 2.12.x series.

  • 0024186[security] Update Parsedown library to 1.7.1 (dregad)
  • 0024097[ui] Account page required change password on any field modification (atrol)
  • 0024090[ui] Username (Realnames) format not showing on timeline (my_view_page) (vboctor)
  • 0024161[timeline] Wrong color of username in timeline (atrol)
  • 0024167[bugtracker] History entries display realname instead of username (atrol)

Go ahead and download the release from our website.

2 thoughts on “MantisBT 2.13.1 and 2.12.2 released”

  1. I say the problem of 2.13.1 version of Mantis.1. After setting $g_show_realname=ON in config_inc.php, the Mantis interface cannot display the realname.2. The reporter receives no mail;3. The email format received by Mantis contains label.

Comments are closed.