<?xml version="1.0" encoding="utf-8"?>
<!--RSS generated by Flaimo.com RSS Builder [2026-11-17 08:37:11]-->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"><channel><docs>https://mantisbt.org/bugs/</docs><link>https://mantisbt.org/bugs/</link><description><![CDATA[MantisBT - Issues]]></description><title>MantisBT - Issues</title><image><title>MantisBT - Issues</title><url>https://mantisbt.org/bugs/images/mantis_logo.png</url><link>https://mantisbt.org/bugs/</link><description><![CDATA[MantisBT - Issues]]></description></image><language>en</language><category>All Projects</category><ttl>10</ttl><dc:language>en</dc:language><sy:updatePeriod>hourly</sy:updatePeriod><sy:updateFrequency>1</sy:updateFrequency><item><title>0037498: MantisCoreFormatting plugin: update prism.js to 2.x</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37498</link><description><![CDATA[PrismJS development for upcoming v2 is moving forward. The project recently tagged the first alpha release, [v2.0.0-alpha.1](&lt;a href=&quot;https://github.com/PrismJS/prism/releases/tag/v2.0.0-alpha.1&quot; rel=&quot;noopener,nofollow&quot;&gt;https://github.com/PrismJS/prism/releases/tag/v2.0.0-alpha.1&lt;/a&gt;).&lt;br /&gt;
&lt;br /&gt;
According to the PrismJS maintainer, the new version fixes the bug with Lisp and Dart languages (&lt;a href=&quot;https://github.com/PrismJS/prism/issues/3789&quot; rel=&quot;noopener,nofollow&quot;&gt;https://github.com/PrismJS/prism/issues/3789&lt;/a&gt;) that was manually patched as part of &lt;a href=&quot;https://mantisbt.org/bugs/view.php?id=34124&quot;&gt;0034124&lt;/a&gt; implementation.&lt;br /&gt;
&lt;br /&gt;
We should test v2 to confirm the bug is indeed gone, and also identify and report any potential incompatibilities upstream.]]></description><category>ui</category><pubDate>Mon, 16 Nov 2026 05:24:22 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37498</guid><comments>https://mantisbt.org/bugs/view.php?id=37498#bugnotes</comments></item><item><title>0037497: Add a search filter to the Manage Projects page</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37497</link><description><![CDATA[The Manage Users page has a search box to narrow down the list of accounts, but Manage Projects always lists every project. On installations with many projects and subprojects, finding one means scrolling through the whole list or using the browser's find.&lt;br /&gt;
&lt;br /&gt;
I'd like to add a search box to Manage Projects, similar to the one on Manage Users, that matches the project name and description. It would use the same syntax: several terms must all match, quoted phrases stay together, and a leading dash excludes a term.&lt;br /&gt;
&lt;br /&gt;
When a subproject matches, its parent projects would still be listed so it keeps its place in the hierarchy. The search would also be kept when changing the sort order.&lt;br /&gt;
&lt;br /&gt;
I have a patch ready and will submit a pull request.]]></description><category>administration</category><pubDate>Wed, 11 Nov 2026 11:55:53 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37497</guid><comments>https://mantisbt.org/bugs/view.php?id=37497#bugnotes</comments></item><item><title>0037496: Update PHPMailer to 7.2.0</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37496</link><description><![CDATA[[PHPMailer 7.2.0](&lt;a href=&quot;https://github.com/PHPMailer/PHPMailer/releases/tag/v7.2.0&quot; rel=&quot;noopener,nofollow&quot;&gt;https://github.com/PHPMailer/PHPMailer/releases/tag/v7.2.0&lt;/a&gt;) has been released.&lt;br /&gt;
&lt;br /&gt;
PR &lt;a href=&quot;https://github.com/mantisbt/mantisbt/pull/2314&quot; rel=&quot;noopener,nofollow&quot;&gt;https://github.com/mantisbt/mantisbt/pull/2314&lt;/a&gt;]]></description><category>email</category><pubDate>Wed, 11 Nov 2026 07:43:08 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37496</guid><comments>https://mantisbt.org/bugs/view.php?id=37496#bugnotes</comments></item><item><title>0037495: multipart/signed parsing loses message body after removal of reference parameter</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37495</link><description><![CDATA[Severity: major&lt;br /&gt;
&lt;br /&gt;
Environment:&lt;br /&gt;
- MantisBT 2.28.4&lt;br /&gt;
- EmailReporting 0.15.0-DEV&lt;br /&gt;
- Installed core/Mail/Parser.php is byte-for-byte identical to upstream commit 5c51587a8d0373485e784e9d56675b380f1d38f1.&lt;br /&gt;
&lt;br /&gt;
Impact:&lt;br /&gt;
This is a message-content loss issue affecting S/MIME-signed email.&lt;br /&gt;
&lt;br /&gt;
EmailReporting accepts and associates the message with an issue, but the parser loses the signed message body. The import can therefore appear successful while the actual support request or reply is missing.&lt;br /&gt;
&lt;br /&gt;
This is not a rejection of an untrusted certificate. The problem occurs during MIME content extraction. A test message with a cryptographically valid signature reproduced the issue.&lt;br /&gt;
&lt;br /&gt;
Description:&lt;br /&gt;
Processing a multipart/signed email produces:&lt;br /&gt;
&lt;br /&gt;
    EmailReporting can't handle this mime part. Please report this to the EmailReporting project developers&lt;br /&gt;
    Array key:&lt;br /&gt;
&lt;br /&gt;
In isolated parser tests, the extracted message body is null despite the signed content containing a text/plain body.&lt;br /&gt;
&lt;br /&gt;
Reproduction:&lt;br /&gt;
1. Send the attached .eml as a message to an EmailReporting mailbox, preserving its MIME structure.&lt;br /&gt;
2. Allow the scheduled mailbox import to process it.&lt;br /&gt;
3. Check the EmailReporting log and the imported content.&lt;br /&gt;
&lt;br /&gt;
The attachment has a cryptographically valid S/MIME signature using a self-signed test certificate. Certificate trust is not implied.&lt;br /&gt;
&lt;br /&gt;
Confirmed end-to-end:&lt;br /&gt;
The attached message was sent through SMTP and processed by EmailReporting on 2026-11-10. It reproduced the exact warning:&lt;br /&gt;
&lt;br /&gt;
    Nov 10 09:51:01 madness bug_report_mail[323917]: EmailReporting can't handle this mime part. Please report this to the EmailReporting project developers&lt;br /&gt;
    Nov 10 09:51:01 madness bug_report_mail[323917]: Array key:&lt;br /&gt;
&lt;br /&gt;
The same import subsequently associated the message with the intended test issue. Body loss was independently confirmed in isolated tests using the identical parser.&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
Commit 2d4141e79fea809fbe5932b230936ee02e3fab83 removed the reference parameter from:&lt;br /&gt;
&lt;br /&gt;
    private function parse_signed_content( &amp;$structure )&lt;br /&gt;
&lt;br /&gt;
The method removes msg_body/sig_hdr/sig_body from the shared structure object. It then assigns the merged decoded structure only to its local variable, so the caller does not receive the decoded message body.&lt;br /&gt;
&lt;br /&gt;
For a signed text/plain body, an empty parts array also remains after removing the signature fields. setParts() rejects this array and prints the warning with an empty array key.&lt;br /&gt;
&lt;br /&gt;
Isolated diagnostic tests:&lt;br /&gt;
- Original parser, signed message: exact warning; body is null.&lt;br /&gt;
- Unsigned multipart control: no warning; body is extracted.&lt;br /&gt;
- Restoring the reference parameter: body is extracted, but the warning remains.&lt;br /&gt;
- Additionally removing the empty parts property: body is extracted without the warning.&lt;br /&gt;
&lt;br /&gt;
Tests used PHP 8.2 with the installed parser and dependencies, without loading MantisBT or accessing a mailbox.&lt;br /&gt;
&lt;br /&gt;
Expected:&lt;br /&gt;
Import the content of signed messages completely. Successful issue association must not conceal loss of the message body.&lt;br /&gt;
&lt;br /&gt;
No production code was modified. The diagnostic changes have not been validated against complex nested MIME structures.]]></description><category>General</category><pubDate>Tue, 10 Nov 2026 13:31:30 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37495</guid><comments>https://mantisbt.org/bugs/view.php?id=37495#bugnotes</comments></item><item><title>0037492: GET /api/rest/issues runs the same DB queries again for every issue in the page</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37492</link><description><![CDATA[GET /api/rest/issues loads the data of each issue in the page one by one:&lt;br /&gt;
bug text, attachments, notes, relationships, monitors and history.&lt;br /&gt;
So the number of DB queries grows with the page size, and a page of&lt;br /&gt;
50 issues runs hundreds of queries.&lt;br /&gt;
&lt;br /&gt;
Some queries are also repeated in the same request:&lt;br /&gt;
- tag_get_by_name() runs once for every tag line in the history,&lt;br /&gt;
  even for the same tag.&lt;br /&gt;
- When a project has no custom fields, an empty list is passed to&lt;br /&gt;
  custom_field_cache_array_rows(), which then loads all custom fields.&lt;br /&gt;
&lt;br /&gt;
What needs to change:&lt;br /&gt;
- Load the data of all issues in the page at once, only for the&lt;br /&gt;
  requested fields.&lt;br /&gt;
- Cache tags found by tag_get_by_name() for the request.&lt;br /&gt;
- Skip loading custom fields when the project has none.&lt;br /&gt;
- Clear these caches whenever the data is written, so a write is&lt;br /&gt;
  seen by the next read.&lt;br /&gt;
&lt;br /&gt;
The response must stay the same. The web UI would also get faster,&lt;br /&gt;
because the caches would be in the core APIs.]]></description><category>api rest</category><pubDate>Fri, 06 Nov 2026 08:23:21 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37492</guid><comments>https://mantisbt.org/bugs/view.php?id=37492#bugnotes</comments></item><item><title>0037491: GET /api/rest/filters returns 500 when a saved filter has a category</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37491</link><description><![CDATA[**Problem**&lt;br /&gt;
`GET /api/rest/filters` returns 500 when any saved filter the user can see (including public ones) filters on a category. One such filter breaks the whole list for every user on the instance.&lt;br /&gt;
&lt;br /&gt;
**Cause**&lt;br /&gt;
Saved filters store the category **name** (e.g. `&quot;Desarrollo de Software&quot;`), but `FilterConverter::convertCategoryArrayToJson()` looks it up as a category **id**. The name is cast to `0`, the category isn't found, and `category_api.php:384` throws `ERROR_CATEGORY_NOT_FOUND`.&lt;br /&gt;
Names that start with a number (e.g. `&quot;1. Numbered&quot;`) are cast to that number, so the API can silently return the wrong category.&lt;br /&gt;
&lt;br /&gt;
**Fix needed**&lt;br /&gt;
Return the stored category name as is (`{ &quot;name&quot;: &quot;...&quot; }`) instead of looking it up by id. Add REST tests for a filter with categories, including a number-prefixed name.]]></description><category>api rest</category><pubDate>Fri, 06 Nov 2026 07:29:06 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37491</guid><comments>https://mantisbt.org/bugs/view.php?id=37491#bugnotes</comments></item><item><title>0037486: MantisGraph : issues_trend_graph.php - invalid render</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37486</link><description><![CDATA[Data track &quot;Still Open&quot; is below &quot;Reported&quot; then not visible.&lt;br /&gt;
Values are OK]]></description><category>plug-ins</category><pubDate>Wed, 04 Nov 2026 08:19:15 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37486</guid><comments>https://mantisbt.org/bugs/view.php?id=37486#bugnotes</comments></item><item><title>0037471: ERROR 2800 (invalid form security token) on login after idle time on username field when typing manually</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37471</link><description><![CDATA[Hello,&lt;br /&gt;
&lt;br /&gt;
After enabling form security validation ($g_form_security_validation = ON), APPLICATION ERROR #2800 (&quot;Invalid form security token&quot;) occurs on the login flow under a specific condition.&lt;br /&gt;
&lt;br /&gt;
Environment:&lt;br /&gt;
- MantisBT 2.28.3&lt;br /&gt;
- $g_form_security_validation = ON (required; we cannot turn it OFF for security remediation and company guidelines)&lt;br /&gt;
- Login is the two-step flow: login_page.php (username) → login_password_page.php (password) → login.php&lt;br /&gt;
- Browser: [Chrome / Edge]&lt;br /&gt;
- OS: [Windows]&lt;br /&gt;
&lt;br /&gt;
Actual result:&lt;br /&gt;
APPLICATION ERROR #2800 – Invalid form security token. The message suggests session timeout or accidental double submit.&lt;br /&gt;
&lt;br /&gt;
Expected result:&lt;br /&gt;
Login should succeed, or the user should get a clear “session expired, please reload” without a hard 2800 after only &lt;a href=&quot;https://mantisbt.org/bugs/view.php?id=7#c15&quot; class=&quot;resolved&quot;&gt;0000007:0000015&lt;/a&gt; minutes of idle on the username field with CSRF enabled.&lt;br /&gt;
&lt;br /&gt;
Additional observations:&lt;br /&gt;
- If, after the same idle period, the username is chosen from the browser’s suggested/autofill list (click suggestion) instead of typing, the error does NOT occur.&lt;br /&gt;
- The issue appears only when typing the username after idle; autofill click works.&lt;br /&gt;
- So far we only see this on the login flow, not on other forms (still under test).&lt;br /&gt;
- We keep $g_form_security_validation = ON on purpose (CSRF remediation). We are not asking to disable form tokens.&lt;br /&gt;
&lt;br /&gt;
Screenshot of ERROR #2800 is attached.&lt;br /&gt;
&lt;br /&gt;
Questions for developers:&lt;br /&gt;
1. Is ~ 15 minutes idle on login_page expected to invalidate the form token while the PHP session may still be alive?&lt;br /&gt;
2. Is there a recommended pattern for the username → password login steps (token lifetime, purge, PRG) so idle + manual typing does not hit 2800?&lt;br /&gt;
3. Any known interaction between form security tokens and browser autofill vs manual input on the login forms?&lt;br /&gt;
&lt;br /&gt;
Thank you for any guidance.&lt;br /&gt;
&lt;br /&gt;
Best regards]]></description><category>security</category><pubDate>Fri, 06 Nov 2026 13:36:09 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37471</guid><comments>https://mantisbt.org/bugs/view.php?id=37471#bugnotes</comments></item><item><title>0037470: config_inc.php.sample outdated</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37470</link><description><![CDATA[e.g. the setting $g_path is not present. This setting file should list all settings that have to be set.]]></description><category>installation</category><pubDate>Fri, 30 Oct 2026 11:44:00 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37470</guid><comments>https://mantisbt.org/bugs/view.php?id=37470#bugnotes</comments></item><item><title>0037469: Bug Tracker discards user input without warning if form is submitted after session has expired</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37469</link><description><![CDATA[This has happened many times now. I logged in, clicked 'Report Issue', and filled in the fields. When I clicked 'Submit Issue', the following error appeared:&lt;br /&gt;
&lt;br /&gt;
APPLICATION ERROR #2800&lt;br /&gt;
Invalid form security token. This could be caused by a session timeout, or accidentally submitting the form twice.&lt;br /&gt;
Please use the &quot;Back&quot; button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.&lt;br /&gt;
&lt;br /&gt;
Clicking the 'Back' button returned me to the the previous page, but all of the entered text was gone and I had to type it again from the beginning. This is very frustrating.&lt;br /&gt;
&lt;br /&gt;
This can also happen when adding a note to an existing incident.]]></description><category>bugtracker</category><pubDate>Tue, 10 Nov 2026 04:14:09 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37469</guid><comments>https://mantisbt.org/bugs/view.php?id=37469#bugnotes</comments></item><item><title>0037467: use html-colgroup in selectors, e.g. category</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37467</link><description><![CDATA[If you use subprojects and define the categories on top of the project, the categories get prefixed by &quot;[project]&quot;.&lt;br /&gt;
This is &quot;ok&quot; in general, but it makes everything very long.&lt;br /&gt;
&lt;br /&gt;
I suggest using colgroups which makes it easier to read/use. It would look like this in the browser:&lt;br /&gt;
Project1&lt;br /&gt;
  cat1&lt;br /&gt;
  cat2&lt;br /&gt;
Project2&lt;br /&gt;
  cat1&lt;br /&gt;
&lt;br /&gt;
I guess this could be applied to other select elemts too.]]></description><category>bugtracker</category><pubDate>Fri, 30 Oct 2026 06:39:17 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37467</guid><comments>https://mantisbt.org/bugs/view.php?id=37467#bugnotes</comments></item><item><title>0037466: Add bug table indexes on (project_id, status) and last_updated</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37466</link><description><![CDATA[mantis_bug_table has separate indexes on project_id and status, but none on both together, and none on last_updated.&lt;br /&gt;
&lt;br /&gt;
A filter that hides closed issues runs:&lt;br /&gt;
&lt;br /&gt;
    WHERE project_id = X AND status IN (...)&lt;br /&gt;
&lt;br /&gt;
MySQL can use only one of the two indexes, so on large things it reads all issues of the project (or all open issues of all projects) to show one page. Filters on last_updated read the whole project.&lt;br /&gt;
&lt;br /&gt;
Proposed: a new upgrade step that adds&lt;br /&gt;
- idx_bug_project_status on (project_id, status)&lt;br /&gt;
- idx_bug_last_updated on (last_updated)]]></description><category>sql</category><pubDate>Fri, 30 Oct 2026 06:47:47 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37466</guid><comments>https://mantisbt.org/bugs/view.php?id=37466#bugnotes</comments></item><item><title>0037464: Email address inputs are limited to 64 characters although the DB column holds 191</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37464</link><description><![CDATA[user.email was created as C(64). Schema upgrade step 208 widened it to C(191), and step 211 did the same for email.email. The HTML email inputs still have a hard-coded maxlength=&quot;64&quot;, so the browser won't accept an email address longer than 64 characters, even though the database can store it.&lt;br /&gt;
&lt;br /&gt;
Affected inputs:&lt;br /&gt;
&lt;br /&gt;
core/print_api.php:245: print_email_input(), which is used by account_page.php, manage_user_create_page.php and manage_user_edit_page.php&lt;br /&gt;
signup_page.php:95&lt;br /&gt;
lost_pwd_page.php:106]]></description><category>ui</category><pubDate>Wed, 28 Oct 2026 10:30:06 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37464</guid><comments>https://mantisbt.org/bugs/view.php?id=37464#bugnotes</comments></item><item><title>0037460: Adding a note to a read-only issue is denied when "All Projects" is selected, although allowed by the project's threshold</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37460</link><description><![CDATA[bug_is_readonly() reads $g_bug_readonly_status_threshold for the issue's project, but $g_update_readonly_bug_threshold for the user's currently selected project.&lt;br /&gt;
&lt;br /&gt;
When update_readonly_bug_threshold is overridden at project level, the result therefore depends on the project selector. view.php overrides the current project, so the &quot;Add Note&quot; form is shown, but when the note is submitted, bugnote_add.php -&gt; IssueNoteAddCommand::validate() -&gt; bug_is_readonly() evaluates the threshold for &quot;All Projects&quot; and rejects the note:&lt;br /&gt;
&lt;br /&gt;
APPLICATION ERROR #1103: The action cannot be performed because issue &quot;X&quot; is read-only. (HTTP 403)&lt;br /&gt;
&lt;br /&gt;
If the user selects the issue's project first, the note is added.]]></description><category>authentication</category><pubDate>Mon, 26 Oct 2026 05:12:44 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37460</guid><comments>https://mantisbt.org/bugs/view.php?id=37460#bugnotes</comments></item><item><title>0037459: Resolution field missing when closing a reopened issue</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37459</link><description><![CDATA[hen an issue that has been reopened is closed directly from the &quot;Change Status To: closed&quot; page, the Resolution field is not shown, so the resolution cannot be set and stays at &quot;reopened&quot;.&lt;br /&gt;
&lt;br /&gt;
bug_change_status_page.php considers the current resolution as &quot;fixed&quot; if it is &gt;= $g_bug_resolution_fixed_threshold (FIXED). With the default enum, REOPENED (30) is greater than FIXED (20), so a reopened issue is treated as already fixed and the Resolution field is hidden when closing it. When resolving a reopened issue, the field is shown but &quot;reopened&quot; is preselected instead of &quot;fixed&quot;.&lt;br /&gt;
&lt;br /&gt;
bug_update.php already treats $g_bug_reopen_resolution as a special case in its resolution checks (see &lt;a href=&quot;https://mantisbt.org/bugs/view.php?id=22468&quot;&gt;0022468&lt;/a&gt; for the original change on the status page).]]></description><category>ui</category><pubDate>Mon, 26 Oct 2026 05:15:09 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37459</guid><comments>https://mantisbt.org/bugs/view.php?id=37459#bugnotes</comments></item><item><title>0037458: Database schema differences for old MantisBT versions updated to recent versions</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37458</link><description><![CDATA[I happen to have a very old MantisBT MySQL/MariaDB database that has been updated over time to 2.28.4.&lt;br /&gt;
I also made a clean MantisBT 2.28.4 install.&lt;br /&gt;
I compared the two database structures.&lt;br /&gt;
Most differences are the text and longtext column types. But there is also a primary index and default value difference.]]></description><category>db schema</category><pubDate>Tue, 03 Nov 2026 13:03:31 -0500</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37458</guid><comments>https://mantisbt.org/bugs/view.php?id=37458#bugnotes</comments></item><item><title>0037457: mci_file_add does not apply proper value for bugnote_id</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37457</link><description><![CDATA[In the /admin/schema.php it says the following.&lt;br /&gt;
&lt;br /&gt;
```&lt;br /&gt;
# 0 - file was added pre-2.23.0 and not explicitly linked to an issue or a note.&lt;br /&gt;
# null - file was added by 2.23.0 release or newer and associated with the issue.&lt;br /&gt;
# otherwise - file was added or linked by 2.23.0 release or newer and associated with an issue note.&lt;br /&gt;
$g_upgrade[210] = array( 'AddColumnSQL', array( db_get_table( 'bug_file' ), &quot;&lt;br /&gt;
	bugnote_id			I		UNSIGNED DEFAULT '0' &quot; ) );&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
mci_file_add does not respect this and always sets the bugnote_id to 0&lt;br /&gt;
I think this has to do with the default value being 0 and NULL not being specifically provided when adding the attachment.]]></description><category>api soap</category><pubDate>Mon, 26 Oct 2026 07:43:38 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37457</guid><comments>https://mantisbt.org/bugs/view.php?id=37457#bugnotes</comments></item><item><title>0037451: string_get_bug_view_link() passes project_id as the $p_user argument to get_enum_element()</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37451</link><description><![CDATA[In `core/string_api.php`, `string_get_bug_view_link()` builds the status label for the link's `title` attribute with this call:&lt;br /&gt;
&lt;br /&gt;
```php&lt;br /&gt;
$t_project_id = bug_get_field( $p_bug_id, 'project_id' );&lt;br /&gt;
$t_status = string_attribute( get_enum_element( 'status', bug_get_field( $p_bug_id, 'status' ), $t_project_id ) );&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
However, the signature of `get_enum_element()` (in `core/helper_api.php`) is:&lt;br /&gt;
&lt;br /&gt;
```php&lt;br /&gt;
function get_enum_element( $p_enum_name, $p_val, $p_user = null, $p_project = null )&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
So `$t_project_id` is being passed as the **third** argument (`$p_user`), not the **fourth** (`$p_project`). Internally `get_enum_element()` forwards both to `config_get( 'status_enum_string', null, $p_user, $p_project )`, meaning the bug's project id is used as a user id when resolving the `status_enum_string` configuration.&lt;br /&gt;
&lt;br /&gt;
Effect: the status label shown in the bug link tooltip does not honor a per-project override of `status_enum_string`, and the project id is mistakenly treated as a user id. In most installations the impact is negligible, because `status_enum_string` is rarely overridden per user and `config_get` falls back to the global value — which is likely why it went unnoticed. But it is still incorrect: a per-project `status_enum_string` override is ignored, and under specific user-level overrides the resolved label could be wrong.&lt;br /&gt;
&lt;br /&gt;
Expected: the project id should be passed as the fourth argument:&lt;br /&gt;
&lt;br /&gt;
```php&lt;br /&gt;
$t_status = string_attribute( get_enum_element( 'status', bug_get_field( $p_bug_id, 'status' ), null, $t_project_id ) );&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
- Confirmed present in the installed version and still present in 2.28.1 and 2.28.4 (latest checked), so this is long-standing, not a recent regression.&lt;br /&gt;
- The resolved-class computation a few lines below already resolves the project correctly, via `config_get( 'bug_resolved_status_threshold', null, null, $t_project_id )` (project as the 4th argument) — which highlights the inconsistency in the `get_enum_element()` call.]]></description><category>bugtracker</category><pubDate>Sun, 18 Oct 2026 22:04:31 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37451</guid><comments>https://mantisbt.org/bugs/view.php?id=37451#bugnotes</comments></item><item><title>0037450: Session lock during shutdown email delivery delays issue pages after updates</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37450</link><description><![CDATA[After adding a note or updating an issue, the redirected issue page&lt;br /&gt;
intermittently takes 5–15 seconds to load.&lt;br /&gt;
&lt;br /&gt;
email_shutdown_function() calls fastcgi_finish_request() and then&lt;br /&gt;
email_send_all() while retaining the PHP session lock. The browser&lt;br /&gt;
receives the response and follows the redirect, but the next request&lt;br /&gt;
using the same session blocks in session_start() until email&lt;br /&gt;
processing finishes.&lt;br /&gt;
&lt;br /&gt;
PHP-FPM slowlog captured nine affected requests, all waiting in&lt;br /&gt;
session_start() at core/session_api.php:149.&lt;br /&gt;
&lt;br /&gt;
Expected behavior: save and release the active session before&lt;br /&gt;
finishing the response and processing notification emails.]]></description><category>email</category><pubDate>Fri, 16 Oct 2026 06:03:52 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37450</guid><comments>https://mantisbt.org/bugs/view.php?id=37450#bugnotes</comments></item><item><title>0037449: Accessibility: Contrast ratio of text in bug_update_page.php fails WCAG</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37449</link><description><![CDATA[When editing a bug, the color of 'select option', 'input' and 'textarea' is #858585 on background #FFFFFF. The ratio being 3.96:1.&lt;br /&gt;
&lt;br /&gt;
Thus, #858585 fails Web Content Accessibility Guideline (WCAG) success-criterion 1.4.3 and 1.4.6 for text and 1.4.6 for large-scale text.&lt;br /&gt;
&lt;br /&gt;
**Solution**: Enhance text-color to #393939]]></description><category>ui</category><pubDate>Wed, 14 Oct 2026 11:29:59 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37449</guid><comments>https://mantisbt.org/bugs/view.php?id=37449#bugnotes</comments></item><item><title>0037447: summary_page.php without submenu</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37447</link><description><![CDATA[if you go to the summary_page there is no submenu, that leads to the graphic pages, anymore.&lt;br /&gt;
you can call for example the mantis/plugin.php?page=MantisGraph/resolution_graph.php direkt and that page shows the submenu. But without the submenu on summary_page, you cannot navigate the the graphic pages.]]></description><category>reports</category><pubDate>Tue, 27 Oct 2026 11:40:09 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37447</guid><comments>https://mantisbt.org/bugs/view.php?id=37447#bugnotes</comments></item><item><title>0037443: Issue created via REST API with too long value for custom field fails in the middle of operation with 500 error</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37443</link><description><![CDATA[When you create an issue via REST API with a custom field (String type) and send value which is too long, more than 255 characters, it creates an issue but fails during 'INSERT INTO mantis_custom_field_string_table [...]'. Exception is thrown from database that data is too long for column 'value'.&lt;br /&gt;
Issue exists but without all provided values for custom fields and 500 response code is returned.&lt;br /&gt;
&lt;br /&gt;
We were able to find a root cause quite quickly because we found deprecation message in logs:&lt;br /&gt;
Unhandled deprecation warning in /var/www/mantis/core/classes/DbQuery.class.php line 298: 'Passing E_USER_ERROR to trigger_error() is deprecated since 8.4, throw an exception or call exit with a string message instead'.&lt;br /&gt;
&lt;br /&gt;
It fails in:&lt;br /&gt;
&lt;br /&gt;
`if( !$this-&gt;db_result ) {&lt;br /&gt;
			db_error( $this-&gt;db_query_string );&lt;br /&gt;
			trigger_error( ERROR_DB_QUERY_FAILED, ERROR );&lt;br /&gt;
			$this-&gt;db_result = false;&lt;br /&gt;
}`]]></description><category>custom fields</category><pubDate>Mon, 12 Oct 2026 02:14:01 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37443</guid><comments>https://mantisbt.org/bugs/view.php?id=37443#bugnotes</comments></item><item><title>0037436: test</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37436</link><description><![CDATA[rozbite]]></description><category>General</category><pubDate>Fri, 02 Oct 2026 06:23:51 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37436</guid><comments>https://mantisbt.org/bugs/view.php?id=37436#bugnotes</comments></item><item><title>0037434: Support S3 as backend for attachments</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37434</link><description><![CDATA[Currently only Database and File System are supported, but with the ability to deploy on clouds, S3 becomes a great addition to it.]]></description><category>attachments</category><pubDate>Wed, 30 Sep 2026 05:02:48 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37434</guid><comments>https://mantisbt.org/bugs/view.php?id=37434#bugnotes</comments></item><item><title>0037433: wrong time locality</title><author></author><link>https://mantisbt.org/bugs/view.php?id=37433</link><description><![CDATA[test to see if the time locality is not consistent with the local machine]]></description><category>time tracking</category><pubDate>Tue, 29 Sep 2026 11:26:57 -0400</pubDate><guid>https://mantisbt.org/bugs/view.php?id=37433</guid><comments>https://mantisbt.org/bugs/view.php?id=37433#bugnotes</comments></item></channel></rss>
