Details
-
Bug
-
Resolution: Fixed
-
Highest
Description
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Hi everyone,
Thanks for patience with us. We have identified the root cause of this issue and a fix has already been deployed to JIRA Cloud production. The fix has been deployed to all instances.
At this point we consider this issue resolved. If you have any questions, please contact Atlassian Support.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
Summary
After the upgrade in JIRA on Jan/3/2016, several customers were having a long delay in JIRA Incoming Email Handlers. Which didn't seem to be running.
After analysis, we found that a code change that inadvertently bypassed some bridging code that existed between JIRA's current scheduled job parameter format and the format that existed pre JIRA 7.0. As a result, schedules that have not been modified since before 7.0 was deployed may not be read correctly by the scheduler.
Editing the service to some other delay and back to '1' rests the Service and fixes the issue:
Steps to Reproduce
After upgrade, some scheduled jobs are not running. The Scheduler details page shows that the jobs parameters could not be read.
Expected Results
Remain running as scheduled.
Actual Results
Affected jobs do not run.
Workaround
- In the Services (https://instance.atlassian.net/secure/admin/ViewServices!default.jspa) page, find the affected job.
- Go to the Incoming Email page
- Edit the Mail Handler
- Set the delay to the desired interval the handler should be executed (in minutes).
If the value is already set to 1, simply click on Next and Save. - Check in Services page if the Service related to that was update correctly. The Service has the same name.
Attachments
Issue Links
- is related to
-
-
- Closed
-