Javier Garces

Thanks I suppose the behavior can be logical... The main.combodo-autoclose-ticket.php file contains this code: ... while ((time() < $iTimeLimit) && $oToClose = $oSetUserRequest->Fetch()) ... In my enviroment' config : 'cron_max_execution_time' => 25, The $iTimeLimit, I guess it corresponds with cron_max_execution_time Lookin at my cron log with verbose: Starting: 1559297702 (2019-05-31 12:15:02) Planned duration = 25 seconds ... === 2019-05-31 12:15:25 Starting: AutoCloseTicket =======================...

Thanks I suppose the behavior can be logical... The main.combodo-autoclose-ticket.php file contains this code: ... while ((time() < $iTimeLimit) && $oToClose = $oSetUserRequest->Fetch()) ... In my enviroment' config : 'cron_max_execution_time' => 25, The $iTimeLimit, I guess it corresponds with cron_max_execution_time Lookin at my cron log with verbose: Starting: 1559297702 (2019-05-31 12:15:02) Planned duration = 25 seconds ... === 2019-05-31 12:15:25 Starting: AutoCloseTicket =======================...

Hello I'm using the extension AutoCloseTicket but recently I realized that it's not closing all the tickets it should. Investigating I have realized that the reason is because the cron_max_execution_time is exceeded. The problem is that task's next run date is always exactly the last second in which the cron is executed, so the extension detects that this period has been exceeded and stops processing the tickets. How can I change the next run date for this task? Do I change it directly in the database...

I guess you have to build your own extension https://www.itophub.io/wiki/page?id=2_6_0%3Acustomization%3Adatamodel

Hello The itop's default datamodel allows you to specify these dependencies: Application Solution -> Web Application -> Web Server -> Server -> Middleware Instance -> Middleware -> Server ->Database schema -> DB Server -> Server if you want to model the typical web application that depends on a web server, an application server and a database I would use it.

Hello I don't knok if this is a bug ,... I reopen an user request from the portal by clicking on the reopen button and filling in a coment in the public log. After this, the aplication shows me the user request form with the cancel and update buttons If I click on the cancel button it doesn't do anything,... Would not it have to show me the ongoing user request list? I test it over the 2.6 version

Hello Does the obsolescence feature have to work with the portal using the iTop's portal default datamodel? https://www.itophub.io/wiki/page?id=latest%3Afeature%3Aobsolescence For example, if I want to add contats to an user request I can add inactive contacts although I have unchecked the 'Show obsolete data' I have tested it in 2.6 beta version

Hello I think that you have these errors: source_scope: to transition an incident to resolved state, it has to exist a transition from the incident's state to the resolved state ( see the incident life cycle in the datamodel) status in the clone: do you have to clone the incident status to the request status?? apply_stimulus to solution in the retrofit: you have to use 'set' apply_stimulus to resolve: you have to specify the event, not the state I do not know if this can help you: array ( 'source_scope'...