We are experiencing issues with the Tempo Reporting Component....

[steve_josue]

Summary

We are experiencing issues with the Tempo Reporting Component. We need assistance to address specific observations and questions that arose during setup.

Context

While configuring reports for each team, we noticed some discrepancies and had questions regarding the functionality of the Tempo Reporting Component.

Acceptance criteria

• Investigate why hours logged show "no sprint" when they were logged within a sprint.

• Provide a method to filter by a specific sprint, beyond just the date range.

• Ensure that selecting “Show assignees with zero hours logged” only displays users from the relevant project.

[Trudy Claspill]

Hello @steve_josue 

You should reach out to the support team specifically for that app.

You can find their contact information on the Support tab of their app listing in the Atlassian Marketplace.

If you are using the Tempo Timesheets app, that is found here:

https://marketplace.atlassian.com/apps/6572/timesheets-by-tempo-jira-time-tracking?hosting=cloud&tab=support

[David Nickell]

Hello - I recommend focusing on one or two tickets and use the Tempo REST Api for understadning how it has stored and/or is treating the data.   You can find details on the REST Calls here:  https://help.tempo.io/cloudmigration/latest/worklog-rest-apis-for-jira-cloud

I created reports for a client last year that pulled the worklog data through rest... here is a sample of the data you can get (some of, but not all of the fields)

There are at least three date fields associated with the entries -- created, updated, and started.  I'm not sure who is making the "in sprint / out of sprint" determination, but I will SPECULATE there may be some sprint date to tempo date issues you're encountering.   I would look for edge cases -- perhaps tickets with time reported near the start or end of a sprint.

Good luck !