Mantis Bug Tracker - Forums

Suggest to try it on a test system.
You can try to go straight to version 2.
If that fails, would try a 3 step approach
first to 1.10
next to 1.20
finally to 2.x

You need an account with sufficient rights on the LDAP server.

There is only a limit on the number of characters, not on words.
The field Description can hold up to 4GB, what do you mean extending??

wel, here is a workaround.
Check if the bug-id's you want to use, are not already used
Remove autoincrement from that table in full ( ensure no users are active in the system)
Once done enable autoincrement on the ID-field and ensure it has a safe value (+1on the highest value)

no, not out of the box. It is send to the admin creating the account

so the plugin is not ready for Mantis 2.x, contact the developer....

Visit this page where you adjust the workflow:
manage_config_workflow_page.php

So you remove the column "Assignee", it is an available setting.

You can adjust the settings for anonymous usage to enable what you want. Adjust this setting: $g_allow_anonymous_login = OFF, set it to ON Next create an account for this usage ( Can be called anything you like) and give it the role of "REPORTER" All set but be ready for a flood of tickets...

You will need to change the PHP file ( with every update again).

In case it happens, I print the issue first so I cannot forget my data....

In the plugin directory there is a mantis.dtd file which looks to me as a nice definition.....

Depends on what you really want. Public tickets are only visible to those who have access to the project it is within. In addition, you can configure the default value with the setting "default_bug_view_status". In case you would like to remove "public" in total, you would need t...

Nee, voor all Nederlandstaligen op deze aardkloot. Maar tot nu toe blijkt de behoeft erg minimaal dus verwacht niet dat er een aparte sectie zal komen.

It worked perfect with version 1 of Mantis.
In case there is enough interest, I could provide an upgrade to version 2.