-
Notifications
You must be signed in to change notification settings - Fork 728
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: mantisbt/mantisbt
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 8d35e57a9977
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: mantisbt/mantisbt
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: f9b9e2fc4356
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 3 commits
- 4 files changed
- 1 contributor
Commits on Jul 3, 2012
-
Fix system warning in html_status_legend() with custom status
When using custom status for which no language strings are defined, html_status_legend() triggered system warnings. MantisBT now displays the custom status' name as defined in the enum, in case there is no available translation string. Fixes #14446
Configuration menu - View commit details
-
Copy full SHA for 123c2c8 - Browse repository at this point
Copy the full SHA 123c2c8View commit details -
Add param to bug_resolve() to allow "resolution" to custom status
Function bug_resolve() sets the status to bug_resolved_status_threshold. This behavior is fine with MantisBT's default status enum, but is causing issues when using a custom target status that is >= $g_bug_resolved_status_threshold & < $g_bug_closed_status_threshold. In this case, when changing status using the button on view.php, the target status selected by the user is overriden by the value of bug_resolved_status_threshold, resulting in incorrect behavior. The only way to effectively reach the custom state is by editing the issue. To address this, a new optional parameter $p_status is added to bug_resolve(). To make the function call more logical, the signature was modified: new parameter inserted in 3rd position after $p_resolution. The function's phpdoc header has been completed. Fixes #14443
Configuration menu - View commit details
-
Copy full SHA for 91a99d9 - Browse repository at this point
Copy the full SHA 91a99d9View commit details -
Code cleanup in bug_update.php
Fixes whitespace, code alignment, typos in comments, long lines
Configuration menu - View commit details
-
Copy full SHA for f9b9e2f - Browse repository at this point
Copy the full SHA f9b9e2fView commit details
There are no files selected for viewing