Why are registered hours in JIRA not syncing to Forecast?

Question

Time registered in JIRA is not appearing in Forecast, why?

Answer

Time registered in JIRA may not sync or appear in Forecast for the following reasons

• Non-synced profile
• Tempo token deprecated
• Project stage
• Time reported on JIRA Epics
• Historical dates 

Non-synced profile

In order for time registrations to sync from JIRA, the corresponding user's Forecast profile must be linked with JIRA. To learn more about how to sync users between JIRA and Forecast see, Connecting JIRA and Forecast user profiles.

Tempo token deprecated

If Tempo is being used for time registration, it may be possible that the Tempo token has been deprecated. When a Tempo token is deprecated, any time registered in Tempo will not sync to Forecast. For more information on using Tempo Timesheets, see Configuring and managing Tempo Timesheets tokens under Additional JIRA sync settings in Syncing JIRA projects to Forecast projects and How to sync time registrations from Tempo to Forecast.

Project stage

Projects in Halted or Done stages are not enabled for editing therefore, if a project is set to Done or Halted stage, time registrations will no longer sync from JIRA. 

See Can I sync Halted or Done stage projects with JIRA? for more information.

Time reported on JIRA Epics

Forecast does not support time registrations at the phase level. Therefore, if time is reported directly on a JIRA epic and JIRA epics are synced as Forecast phases, the time entries in JIRA will not sync or appear in Forecast. To learn more about the various sync settings available for the JIRA integration see, Syncing JIRA projects to Forecast projects. 

Historical dates

Time entered in Jira prior to December 2019 will not sync to Forecast. If you have time registrations dated prior to December 2019, please reach out to Forecast Support.