View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022489 | mantisbt | preferences | public | 2017-03-07 10:06 | 2019-12-03 06:14 |
Reporter | joachimcarrein | Assigned To | |||
Priority | low | Severity | feature | Reproducibility | have not tried |
Status | acknowledged | Resolution | open | ||
Product Version | 2.2.0 | ||||
Summary | 0022489: View Threshold for bugnotes | ||||
Description | It would be convenient for our setup to have a 'view_bugnote_threshold' configuration setting (cf. 'view_history_threshold'). | ||||
Additional Information | We use mantis to manage all our customer projects (+300), mantis is the perfect match for us. In some cases we don't want to disclose too much information about issues to the customer because of obvious reasons.
On our MantisBT 1.x installation we fixed this by directly editing the PHP files (and making a mess). The 'Hide History' we could perfectly implement using a plugin.
We would like to implement the 'hide notes' the same way in our plugin, but we are missing | ||||
Tags | No tags attached. | ||||
I would suggest to simply mark notes as private, and set $g_private_bugnote_threshold as appropriate... |
|
Thanks for the suggestion, The suggested option 'view_bugnote_threshold' would fall straight in line with other mantis features, altough admitted The goal is a fool-proof, water-tight system, with modificiation ONLY done by plugins. |
|
@raptox_be I understand your concerns about the human factor. That being said, unless you're willing to do the legwork and propose a pull request with the necessary code changes, I think it's quite unlikely that we would implement such a feature in the short term. As you said, it's a very specific usage scenario that would not frequently be used by most MantisBT users. |
|
One more thing, following up on the private notes workaround I suggested earlier, you can also set notes view state to private by default ( |
|