View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0031711 | mantisbt | bugtracker | public | 2022-12-04 22:20 | 2023-01-02 07:19 |
Reporter | duongnvm | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Product Version | 2.25.2 | ||||
Summary | 0031711: Reporter was unable to close the issue | ||||
Description | Reporter failed to close the issue, because there is no close button. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
You are not giving much contextual details, but I'm guessing the problem may be due to the fact that the button is only displayed when the Issue is in RESOLVED state (as defined in $g_bug_resolved_status_threshold). This is not consistent with how $g_allow_reporter_close is documented in the Admin guide, but matches the PHPDoc in config_defaults_inc.php, which states
Removing the This check was added in 2012 (MantisBT master 085ab169, see 0014156), matching the PHPDoc specification. Now the question is, what is the correct / intended behavior ? |
|
Thank you for your reply. |
|