View Issue Details

IDProjectCategoryView StatusLast Update
0037134mantisbtbugtrackerpublic2026-05-31 17:16
Reporterdregad Assigned Todregad  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Target Version2.29.0Fixed in Version2.29.0 
Summary0037134: The "Jump to bug" form should accept bug_id with leading #
Description

Currently, the form only accepts integer values, causing an error to be thrown f the user enters #1234 in the search field, which sometimes happen when copy/pasting e.g from a Git commit message.

As a convenience, we should also allow integers prefixed by the configured tag ($g_bug_link_tag, # by default).

TagsNo tags attached.

Activities

Related Changesets

MantisBT: master 9b0f1a52

2026-05-17 11:23

dregad


Details Diff
Allow bug_link_tag prefix in jump to bug form

Until now, due to the use of gpc_get_int(), an error was thrown if the
user entered `#1234` in the search field, which sometimes happen when
copy/pasting e.g from a Git commit message.

As convenience, we now ignore the leading `#` (technically, the value of
$g_bug_link_tag config) and extract the bug id from the rest of the
string.

Fixes 0037134
Affected Issues
0037134
mod - jump_to_bug.php Diff File

MantisBT: master d67d5024

2026-05-17 11:24

dregad


Details Diff
Move print bug jump form code to its own function

New layout_bug_jump_form() function extracted from layout_breadcrumbs().

Use printf() instead of concatenated echo for cleaner code.

Issue 0037134
Affected Issues
0037134
mod - core/layout_api.php Diff File

MantisBT: master 06584820

2026-05-29 19:38

dregad


Details Diff
Use the first group of numbers as bug id

As suggested by @atrol in PR review,

Fixes 0037134
Affected Issues
0037134
mod - jump_to_bug.php Diff File