Categories when moving an issue to another project
KM <info4km-/[email protected]> Fri, 7 Feb 2014 08:31:13 -0800 (PST)
| Newsgroups | gmane.comp.bug-tracking.mantis.general |
|---|---|
| Message-ID | <[email protected]> |
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. For example I have issue 0111333 in xyz project w/ category "Administration". I move the issue to abc project where Administration is not a valid category. Currently (1.1.7) it just moves it and keeps the invalid category. 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. If not - does anyone know if there is an easy way to possibly write a custom function to do this on a move? I know these are general questions - but any help is always appreciated. Thanks KM ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/mantisbt-help