Mantis Bug Tracker - Forums

We have got a problem with the new user procedure. The problem ist that a new user is not able to setup his password. The new user receives via e-mail the link to set password screen, but the new password is never set. The same problem occurs as well in the change password procedure.

Debugging the ...

I don't no if there's some default technical integration between both systems. It would make sense, since there might be relationships between incidences and bugs. Anyway in our case it was not worth to do that.

From my point of view the main difference between bugtracking and ticketing is that the user's of both types of solution are different and have different needs. Functionality might be similar, but differs in the details.

We are using Mantis for bugs and OTRS (http://www.otrs.org) for ticketing.

Thanx vboctor.

We installed Mantis in our LAN and all the stuff worked well. Later we moved Mantis to our ISP (new installation of Mantis, export/import of existing database) on a virtual server. All works fine except the creation of new users and the password change. In both cases you receive via ...

Thanx for your answer. So let's forget logging. What's the common way in Mantis to find out the reasons why something is not working well? Last option is always debugging the code, but we would prefer not doing that. If debugging is the only way, that's ok, but I would like to know before.

We 've got some problems with the password change procedure. We suppose that 's about a configuration problem and we'd like to see if some exceptions are produced, but we do not know where to configure the creation of a log-file.

Does anybody know what to do? Thanx a lot in advance.