Summary

The Next run time shown for 'com.atlassian.jira.service.JiraService:10000' under Scheduler Administration is incorrect (it shows the time JIRA approximately starts up) and does not update.

Note: 'com.atlassian.jira.service.JiraService:10000' refers to the Mail Queue Service 'com.atlassian.jira.service.services.mail.MailQueueService'.

Environment

• JIRA Server 7.0.5
• JIRA Server 7.2.8
• JIRA Server 7.3.7
• JIRA Server 7.4.0
• JIRA Server 7.4.1

Steps to Reproduce

1. Go to Scheduler Administration (under System -> Scheduler details)
2. Click 'Show more' for 'com.atlassian.jira.service.DefaultServiceManager'
3. Take note of Last run and Next run time/date for 'com.atlassian.jira.service.JiraService:10000'
4. Wait for a minute, and then refresh the page and check the time/date again

Expected Results

The Next run time should be later than the Last run time for 'com.atlassian.jira.service.JiraService:10000'. The cron time used for scheduling is '0 * * * * ?', and as such there should be a minute's interval between the Last run time and Next run time.

Actual Results

The Next run time stays the same while the Last run time gets updated every minute. Next run time appears to show the time that JIRA instance started and it does not change.

Impact

Since the Last run time does get updated every minute, it means that the Scheduler is working as expected. Therefore, the impact of this bug is Low.

Workaround

None yet