Mantis Bug Tracker - Forums

Having Mantis 1.2.5 and using Testlink 1.9.6 the integration by SOAP goes fine, but after I make a update into mantis to 1.2.15 version, the integration don't work anymore.

Message into TestCase Execution:
Atención por favor:
Algo está impidiendo la conexión con el Gestor de Defectos,
y está ...

Using $g_view_summary_threshold (supposes that specifies the access level required to view the summary page) is not possible?

I wonder the same; is possible to add custom field to profile, so entire profile information could be added at once while reporting bugs just by choosing profile?
Thanks

Sorry Atrol, really wasn't my intention generate confusion...
Anyway, analyzing again posts I finally found the solution about original request: in a determined option "severity_enum_string" to a selected and particular project, I change type complex to string, and values in array to a simple list ...

I just followed your steps, strictly:

1) Install Mantis2Go 1.0.10 (= MantisBT 1.2.15)
2) Create a new project
3) Goto page Manage > Manage Configuration > Configuration report
4) Create an option for "All Users", "All Projects" , "Configuration Option" priority_enum_string, Type string, Value: 10 ...

In others words, if I follow yours steps, I don't see the custom values when I create a new issue. If I customize to one specific project appears @0@.
Maybe isn't a bug but isn't that I need.

@Atrol:
Even if I follow the steps in your post, the result is: that is, do not displays either the data I need

Do you enter "10:Inmediata,20:Alta,30:Media,40:Baja,50:Urgente" including the quotes?
should be 10:Inmediata,20:Alta,30:Media,40:Baja,50:Urgente
I know, the quotes is only to reference the text inside him.

BTW, why do you use the configuration in database instead of setting the enumeration in ...

Well, resuming after new backup:

1) In PhpMyAdmin import my DB (Production).
2) I Inserted a new commented line in config_inc $g_database_name = 'mantistest'.
3) Change between lines ($g_database_name = 'bugtracker' or $g_database_name = 'mantistest') into config_inc.
3.1) Using your db in Manage ...

Are you really sure that there is no table mantis_category_table in your production environment?
I'll request a new backup of data in production

Maybe you did not import your whole database to Mantis2Go?
After having the new backup, I will resume importation and comparison tables and then ...

There went something wrong when updating from an older MantisBT version.
There are logs after update :?:

one of the first steps when upgrading from version 1.1.x to 1.2.x is the creation of mantis_plugin_table
This happens during upgrade process when running admin/install.php
My first ...

atrol wrote: It should be 183.

Both in my production enviroment, in my test enviroment or my Mantis2Go enviroment always is displaying "Versión de esquema 183"

atrol wrote: Which tables are not in your installation?

Your installation have and not mine:
mantis_bug_revision_table
mantis_category_table
mantis_plugin_table

My installation have and you don't:
mantis_project_category_table

I hope we have found something

It seems that you imported your data to another database than the one you configured in config_inc.php.
Yes, I said it in item 3.
I would like to see a reproducible issue without any import of data, just a clean installation of Mantis2Go and step by step instruction how to reproduce the issue ...

Using Mantis2Go 1.0.10:

1) Was Installed the app in different PC and folder
2) Was imported the data to new database
3) Was replaced the config _inc.php file into "C:\Mantis2Go\Mantis2Go\htdocs\mantisbt"
4) Was placed the custom_strings_inc.php file into same directory described above.
5) Now ...