Re: Backup project data

 >> Ok. I use it a lot indeed. But the filters canonly reduce the amount
 >> of issues on the "View Issues" page.
 >
 > Absolutely it can, and I use this every single day to reduce the view to
 > see only what I need/want to see on the "View Issues" page.
 >
 > Try this:
 >
 > "Hide Status: resolved (And Above)"
 >
 > Ta-da!

Sorry David. You misunderstood me. I agreed with you. I use the view issues 
page to filter all this...
But it can only filter the issues on this page, you know? And it is really not 
my problem!

There are other places polluted by the amount of data and the view issues page 
(filters) cannot help me with.

--
RYAN LEITE ALBUQUERQUE
C.E.S.A.R Software Configuration Management Engineer
55 (81) 3134.5674 (Barbosa Lima)
55 (81) 3134.4851 (Tiradentes)
55 (81) 8727.4111 (Cell)
55 (81) 3342.3753 (Home)
MSN/Email: ryan-/PpS1Qp42A70xEqrn79Vhg@xxxxxxxxxxxxxxxx
Skype: ryanalbuquerque


David A. Desrosiers wrote:
> 
>> It cannot cut down the list of unused projects in my top-right combo
>> or in my list of projects in Manage Project page. 
>> It also cannot cut down the list of unused custom fields...
> 
> Manage -> Manage Projects -> View Status: Private
> 
> That doesn't exactly do what you want, but I do see a small feature that
> can be added here... "Disable Project" or "Archive Project", where it is
> removed from the standard view (and the standard "View Issues" queries),
> until you specifically wish to view it under say... 
> 
> Manage -> Manage Projects -> Archived Projects
> 
> Now, this can get complicated, if you have cross-project bugs and bug
> relationship (bug #1487 in Project_A is related to bug #23 in Project_B,
> which you just archived), etc. 
> 
> Its doable, just not as easy as adding a row to a table. 
> 
>> And it also cannot solve my problem of project specific data
>> migration. Is the only solution to dump the entire database 
>> from the original instance, import it in the new instance and remove
>> unwanted projects? Well, I think it is not an elegant solution...
> 
> I'm not sure why you want to take projects out of one Mantis instance
> and import them into another Mantis instance, that's a bit weird (not to
> mention it will break everything in horrible ways, as all bugs, notes,
> users, etc. are all renumbered and those relationships are attempted to
> be retained). 
> 
> Now let's think of the other way... people (like myself) who are
> _required_ to keep all project data, bugs, etc. online, for compliance
> and legal reasons. What then? 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> mantisbt-dev mailing list
> mantisbt-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/