schedule job next execution time is not correct after manaully running it

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Low
    • None
    • Affects Version/s: 6.8.1
    • Component/s: Server - Administration
    • None
    • 3
    • Severity 3 - Minor
    • 1
    • Hide
      Atlassian Update - 09 April 2020

      This issue has been duplicated by the issue at CONFSERVER-52363 - "Next Execution" in Scheduled Jobs panel displays timestamps in the past

      Please watch that issue for further updates.

      Show
      Atlassian Update - 09 April 2020 This issue has been duplicated by the issue at CONFSERVER-52363 - "Next Execution" in Scheduled Jobs panel displays timestamps in the past Please watch that issue for further updates.

      Description

      When a user manually run the scheduled job, the next execution time will display an incorrect value.

      Steps to reproduce

      1. Access the scheduled job page
      2. Run the send batch notification or flush mail queue schedule job
      3. You will notice that the next execution time is displaying the date and time 2 hours before.

      Expected Result
      The next execution time is the last execution time + duration of the scheduled job

      Actual Result

        1. screenshot-1.png
          screenshot-1.png
          6 kB

            Assignee:
            Unassigned
            Reporter:
            Lipkent Ng (Inactive)
            Votes:
            7 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: