Welcome to Tempo’s Idea Portal! Your suggestions are valuable to us and help us make our products even better.
Below is a list of ideas for Tempo, so please search, review and vote for those that would help you the most. We encourage you to add an idea if you don’t see it listed. You can stay updated on the work we are doing here at Tempo by contributing to this page.
To learn more and see our Frequently Asked Questions, click here.
They have looked into using the Planned vs Actual report which is great to see if an user have logged the required hours, e.g. John has planned to use 50 hours, but has actually logged 75 hours. But perhaps in the logged 75 hours he actually managed to complete work/issues that where estimated to 100 hours - therefore overall the project is in front compared to the scheduled/estimate time.
They have also looked into using the Logged Time Report for Tempo Timesheet, and simply using the Overview and adding Logged, Estimated and Remaining columns. The issue here is that the Logged Time report only displays issues that have logged time on them. Therefore in the Estimated sum up for the Epic I am missing hours since there are some child issues with original estimates that have yet to have work logged and therefore the original estimate of these issues are not included in my sum up of the epic.
To me it seems like Tempo has all the data needed, to provide the requested overview, however no smart way to display it. Time spent/logged hours, remaining hours, original estimate are there and they are summed up from stories/tasks to the parent/Epic by Tempo. Instead of needing to access each epic to get a status an overview through e.g. a dashboard gadget would be just what the client is looking for. Another vendor seems to have solved the issue (https://marketplace.atlassian.com/apps/1219703/time-tracking-estimation-report-dashboard-gadget-for-jira?tab=overview&hosting=cloud) which we will look into now, it is just a shame not being able to use Tempo for this, as the data is there.
A client of mine could really use this as well.
They have looked into using the Planned vs Actual report which is great to see if an user have logged the required hours, e.g. John has planned to use 50 hours, but has actually logged 75 hours. But perhaps in the logged 75 hours he actually managed to complete work/issues that where estimated to 100 hours - therefore overall the project is in front compared to the scheduled/estimate time.
They have also looked into using the Logged Time Report for Tempo Timesheet, and simply using the Overview and adding Logged, Estimated and Remaining columns. The issue here is that the Logged Time report only displays issues that have logged time on them. Therefore in the Estimated sum up for the Epic I am missing hours since there are some child issues with original estimates that have yet to have work logged and therefore the original estimate of these issues are not included in my sum up of the epic.
To me it seems like Tempo has all the data needed, to provide the requested overview, however no smart way to display it. Time spent/logged hours, remaining hours, original estimate are there and they are summed up from stories/tasks to the parent/Epic by Tempo. Instead of needing to access each epic to get a status an overview through e.g. a dashboard gadget would be just what the client is looking for. Another vendor seems to have solved the issue (https://marketplace.atlassian.com/apps/1219703/time-tracking-estimation-report-dashboard-gadget-for-jira?tab=overview&hosting=cloud) which we will look into now, it is just a shame not being able to use Tempo for this, as the data is there.