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
For time registrations to sync from Jira, the Jira user associated with the logged time must be linked to a Forecast team member profile.
For more details on syncing users between Jira and Forecast, see Connecting JIRA and Forecast user profiles.
Tempo token deprecated
If you use Tempo, time will not sync from Jira to Forecast if your Tempo token is deprecated.
For more information on using Tempo Timesheets, see Configuring and managing Tempo Timesheets tokens in Syncing JIRA projects to Forecast projects and How to sync time registrations from Tempo to Forecast.
API user lacking permissions
When syncing worklogs, the API inherits the access levels of the Jira user who generated the Forecast Tempo token. To ensure that all worklogs across every project and employee are successfully imported, that specific Jira account must be granted both the Browse Projects and View All Worklogs permissions.
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.
Comments
0 comments
Article is closed for comments.