View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006150 | mantisbt | bugtracker | public | 2005-08-17 14:52 | 2012-08-17 14:11 |
Reporter | mspears | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.0.0rc1 | ||||
Fixed in Version | 1.2.0 | ||||
Summary | 0006150: Should Category inheritance be a preference? | ||||
Description | Currently, parent projects inherit Categories from subprojects. This creates confusion as to which project Category you're actually reporting. Based on user feedback, would it be possible to disable the Category inheritance as a boolean preference or disallow inheritance completely? | ||||
Tags | No tags attached. | ||||
It would be really useful, if inheritance of categories could be disabled. As an alternative the "namespace" of the category should be displayed (eg. "subproject1.categoryname") |
|
So. Now that I (rather inadvertently) clicked on the "Sponsor"-Button, I owe the Project $10. As I consider this bug an important matter, I'm perfectly willing to pay my debt. But how ? Paypal ? Credid Card ? Actually I don't really understand the whole Sponsorship bussiness ... |
|
I hope there will be a flag added to disable the inheritance of categories, because the autoassignment of bugs does not work properly with it. I modified print_api.php in the installation in my company to disable the inheritance of categories. My temporary solution is: diff print_api.php print_api_new.php486c486,488
|
|
-- just a reminder on this bug -- maybe an option in the config_inc.php can control the where in the query |
|
When creating subprojects there is a checkbox "Inherit Parent Categories" |
|