View Issue Details

IDProjectCategoryView StatusLast Update
0010498mantisbtfilterspublic2019-09-12 15:20
Reportermstedman Assigned To 
Status acknowledgedResolutionopen 
Product Version1.1.6 
Summary0010498: Allow search filter to include issues within "disabled" projects and their children

Currently we have 380 projects in our Mantis. (Yes.. we love the product)
Obviously people would like to limit their project selection drop down for their daily use and we currently do this by removing the "tick" from "Enable" in the project management section.

Unfortunately this results in items from these project no longer being searchable.
There is a great deal of historical information that is useful for decision making today...the ability to include disabled project issues in the search criteria would be really helpful.

Additional Information

Currently we have looked at modifying our install to do this...but it would be nice if this was a formal feature so we could avoid re-adding this change when we upgrade to any new Mantis release.

TagsNo tags attached.


related to 0025564 new Issues in disabled projects are accessible 
has duplicate 0019533 closedatrol [Requirement][Filter] Add a filter option to list disabled projects 
has duplicate 0020153 closedatrol Filter windows : filter on disabled projects ? 
has duplicate 0026131 closedatrol Allow for non-enabled projects to be seen in View Issues 




2015-03-20 09:36

reporter   ~0049278

We also need this feature for our products (cf 0019533).
Cannot we target this ticket already for a next release?
(and why is it still 'new' since it has been created in 2009 ?)

Thank you all.



2015-03-20 12:36

developer   ~0049279

Bozz, It all depends on priority and a developer or community member deciding to spend their time on a specific issue.

Submitting a patch is always a good idea, as it increases the chances of improvement eventually making it into MantisBT core. All contributions are welcome and greatly appreciated.

Patch submissions can be made in several ways. In the order of preference:

  1. Send us a Pull Request on our Github repository [1]
  2. Attach a GIT patch to the issue
  3. Attach a Unified Diff, clearly specifying the patch's base release

Kindly avoid to upload entire modified PHP files.

Please make sure that your submissions adhere to our Coding Guidelines [2], if they don't your patch might be rejected.




2015-03-20 12:44

developer   ~0049280

and why is it still 'new' since it has been created in 2009 ?

OK, now it's acknowledged... better ? ;-)



2015-03-20 14:45

reporter   ~0049282

Great! Thank you. I'll see what I can do then.



2015-03-23 06:31

reporter   ~0049284

I thought that we could make a plugin for that, but actually no :( because of these lines in the filter:
$t_project_where_clauses = array( '{project}.enabled = ' . db_param() );
$t_where_params = array(
1, // <-- Here, always for enabled projects, no matter what.

It seems like, the only way then is really a patch.