Lattice Jira Goal Progress Not Updating
Workaround available Web (Jira Cloud) Updated October 21, 2026
Quick answer
Lattice pulls Jira progress into goals once an hour from a JQL query on Jira Cloud only. Progress looks stuck when the query excludes subtasks, the JQL is invalid, the goal was disconnected, or a Lattice incident hit the integration.
Most likely fix: Wait for the hourly sync.
Symptoms
Goal progress stays at the same percentage, a 'Search error' appears, or Jira issues can't be found when connecting a goal.
Why it happens
- Sync runs at the start of each hour
- JQL query excludes subtasks where the work lives
- Invalid JQL
- Goal disconnected from Jira
- Using Jira Server/Data Center (only Jira Cloud supported)
- Integration incident (e.g. September 2025)
How to fix it
Try these in order — the most common fix is first.
1. Wait for the hourly sync
- Check again after the top of the next hour
2. Fix the JQL query
- Open the goal's Jira connection
- Validate the query in Jira's advanced search
- Expand it to include subtasks if they carry the work
3. Reconnect the goal
- If the goal was disconnected, reconnect it to Jira; disconnected goals no longer update automatically
4. Check status
- Look for Goals/Jira incidents on status.lattice.com
This guide also covers
- lattice jira integration not working
- lattice goals jira progress
- lattice jql search error
Still not working?
If Lattice keeps failing, you're not alone. See every Lattice problem users report or the alternatives people switch to.
Other Lattice errors
- Lattice 1:1 Not Syncing With Outlook or Google Calendar
- Lattice Outlook 'Need Admin Approval' Error
- Lattice 'Something Went Wrong' Error
- Lattice Can't Submit Review
- Lattice Not Sending Email Notifications
- Can't Log Into Lattice (SSO or Invalid Token)
- Lattice Slack Integration Not Working
- Lattice HRIS Integration Not Syncing Employees
- Lattice Review Cycle Not Showing Updated Employee Data
- Lattice HRIS Shutting Down: What Happens to Your Data