View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004354 | mantisbt | bugtracker | public | 2004-08-18 13:26 | 2013-12-01 22:05 |
Reporter | mfroman | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | confirmed | Resolution | open | ||
Product Version | 0.19.0a2 | ||||
Summary | 0004354: fix for bug 0003824 seems to not address private bugnotes | ||||
Description | While the fix seems to address notifications for private bugs, when the patch for 0.18.3 shown in 0003824 is used, it does not fix notifications for private bugnotes. I pulled the code for 0.19.0a2 and it would seem to have the same problem. | ||||
Tags | No tags attached. | ||||
I cannot reproduce this in CVS HEAD. The fix in 0003824 addresses bugs that are marked as private. There is an additional change in bugnote_api.php introduced early in 0.19 to address the private bugnotes issue. What is your $g_private_bugnote_threshold set to? The default is DEVELOPER. What is the access level for the user getting the messages? edited on: 08-18-04 15:27 |
|
I pulled the code from CVS using the two commands listed in the CVS section of the docs: If the code acquired this way does not correspond to CVS HEAD, please let me know and I'll retry the test with code pulled using whatever method you supply. I started with a newly created database, and the code pulled from CVS. With the exception of setting the database fields in the config_inc.php, I was running with a completely default setup.
Let me know if I can provide any other info. to help on this. edited on: 08-19-04 10:34 |
|
But the bugnote itself was not included? Now that I understand your comment, I can reproduce it. |
|
Correct. The bugnote itself was not included in the email. |
|