Thanks. I just looked at the 1.2.x manual and config_defaults_inc.php file and
I see the following info to which you are referring:
/**
* Default global category to be used when an issue is moved from a
project to another
* that doesn't have a category with a matching name. The default is 1
which is the "General"
* category that is created in the default database.
*/
$g_default_category_for_moves = 1;
Once I upgrade I will have to look into using this either as is w/"General" or
defining new ones.
Thanks
KM
________________________________
From: Damien Regad <dre...@mantisbt.org>
To: mantisbt-help@lists.sourceforge.net
Sent: Friday, February 7, 2014 11:44 AM
Subject: Re: [mantisbt-help] Categories when moving an issue to another project
On 07.02.2014 17:31, KM wrote:
> Currently we are using 1.1.7 which is very old. I am going to work on
> upgrading to 1.2.x. However I had a question. Does anyone know if in
> the 1.2.x series if the "Category" field is validated when moving an
> issue from one project to another? I know that in 1.1.7 it is not.
Categories are handled differently in 1.2 - they are identified by a
category ID.
When moving categories to a different project, should the category not
be available in the target project, Mantis would fall back to a default
category (which you can define) so in theory you should not have invalid
categories anymore.
> Will upgrading to 1.2.x fix this and force a user to update the
> category? the same is happening for the versions for the projects.
I am not sure how the upgrade process actually handles this, but I would
assume it follows the same logic of assigning a default category.
> If not - does anyone know if there is an easy way to possibly write a
> custom function to do this on a move?
You can probably do that, but it's probably best managed by manipulating
the data either before or after the upgrade process. I don't recommend
messing with the the installer.
Hope this helps
D
---
This email is free from viruses and malware because avast! Antivirus protection
is active.
http://www.avast.com/
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
mantisbt-help mailing list
mantisbt-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-help
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
mantisbt-help mailing list
mantisbt-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-help
