View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0021030 | mantisbt | sponsorships | public | 2016-05-30 11:58 | 2016-06-12 00:42 |
Reporter | dregad | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Target Version | 1.3.0-rc.2 | Fixed in Version | 1.3.0-rc.2 | ||
Summary | 0021030: Error 1704 assigning a sponsored after sponsorship has been turned off | ||||
Description | It is not possible to assign a previously sponsored issue even when sponsorship has been switched off: APPLICATION ERROR 1704 | ||||
Steps To Reproduce |
| ||||
Tags | No tags attached. | ||||
MantisBT: master 1a4ecfcb 2016-05-31 07:09 Details Diff |
Do not enforce related thresholds when sponsorship is OFF When $g_enable_sponsorship = OFF, we should not enforce related thresholds ($g_handle_sponsored_bugs_threshold and $g_assign_sponsored_bugs_threshold) when updating issues. Fixes 0021030 |
Affected Issues 0021030 |
|
mod - bug_change_status_page.php | Diff File | ||
mod - bug_update.php | Diff File |