Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TicketEscalationSuspendCalculate() expects cron time to be four minutes #389

Closed
bschmalhofer opened this issue Aug 24, 2020 · 1 comment
Closed
Assignees
Labels
invalid The report was either incorrect, or it describes the correct behavior. question Further information is requested
Milestone

Comments

@bschmalhofer
Copy link
Contributor

In Kernel::System::Ticket::TicketEscalationSuspendCalculate() there are these lines:

    # add 4 minutes (time between cron runs) if we are in suspend state to prevent escalation
    if ( $Param{Suspended} ) {
        $UpdateDiffTime += 4 * 60;
    }

It is not obvious where those four minutes come from. In OTOBO the default cron interval is five minutes,

@bschmalhofer bschmalhofer added the question Further information is requested label Aug 24, 2020
@bschmalhofer bschmalhofer added this to the OTOBO 10.1 milestone Aug 24, 2020
@bschmalhofer bschmalhofer modified the milestones: OTOBO 10.1, OTOBO 10.0.4 Oct 1, 2020
@bschmalhofer bschmalhofer added the invalid The report was either incorrect, or it describes the correct behavior. label Oct 1, 2020
bschmalhofer added a commit that referenced this issue Oct 1, 2020
Issue #389: add code comment stating that the job interval must not b…
@bschmalhofer bschmalhofer self-assigned this Oct 1, 2020
@bschmalhofer
Copy link
Contributor Author

The relevant time is the configured in the setting Daemon::SchedulerCronTaskManager::Task###RebuildEscalationIndex.
I added a comment in Kernel/Config/Files/XML/Ticket.xml stating that the four minutes are relevant and should not be changed.
Marking this issue as 'invalid' and closing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid The report was either incorrect, or it describes the correct behavior. question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant