We used Mantis 1.0.8, NuSoap 0.7.2, PHP 5.1.6, Apache 2.2.4 et MySql 2.9.1.1.

Modifications list :

Refactored permission functions :
Because of code redundancy in MantisConnect functions, we refactored all permission functions, using one main check function ( mciCheckAccess ) which take in parameter an array of constants defining the specific check functions to call.
-> mci_access_api.php : function mciCheckAccess

Mantis error handler overriding :
Webservice do only the tests checked in Mantis graphical user interface, not those made by the Mantis core. Error reports returned by Mantis internal tests, are transmitted to the WS client through SOAP error. Before, the same check was sometimes redundantly made, once in MantisConnect, once in Mantis.
-> mci_trigger.php : function mciErrorHandler

Test scenario :
For our devs, we used a testing script which consist in a scenario of successive WS call. That was very usefull for non-regression tests.
-> ./test-integration/scenario_bug.php (we also made some kind of unit test in ./test-unitaire folder )

New services :
We added the following functionalities :

* Issue management (mc_bug_api.php) :
      o update an issue,
      o assign an issue, 
      o change issue status,
      o move issue form a project to another,
      o start/stop issue monitoring,
      o copy an issue,
      o get issue history,
      o send a reminder to a list of users,
      o get the number of notes for an issue, 
      o get issue update date,
      o re-opening an issue,
      o test if user is the issue reporter,
      o test if a user is assigned to an issue,
      o check the "read only" status of an issue.
* Notes management (mc_bugnote_api.php):
      o change note text, 
      o change note visibility, 
      o get all visible note for a user and a bug,
      o check note existence,
      o check if a user is the reporter of a note.
* Attached file management (mc_file_api.php) :
      o check if an issue has attached files, 
      o check if a user can see the attached files, 
      o check if a user can download the attached files,
      o check if a user can delete the attached files,
      o check if a user can add attached files,
      o check if a user can add  files in a project,
      o delete a file,
      o delete all issue attached files,
      o delete all project attached files,
      o get the number of attached files for an issue.
      o upload remain to do :(

* Filter management (mc_filter_api.php),
      o check if a user can delete a filter, 
      o get default filter, 
      o get a filter saved in database,
      o get the name of a filter,
      o get the available filters for a user and a project,
      o add/modify a filter saved in database,
      o delete a filter saved in database,
      o web service used to get filtered bug list has been enhanced and can handle more options.
* Relationship management (mc_relationship_api.php) :
      o check relationship existence,
      o check if an issue can be resolved (are child issue all resolved?),
      o add a relationship,
      o update a relationship,
      o delete a relationship.