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.
In case on an issue it is allowed to log with more than one account, this is essential in reporting. Without this we can only use the reporting in the case of 1account/issue, meanning all account related Tempo functions are useless.
Using different accounts under an issue is recommended by tempo documentation.
Raw data export is a very poor workaround, since there is no option to exclude columns from is, just adding custom jira fields, meaning every single time we use it, we have to manually sort and delete 60-70% of its content before it is useable. This also means we do not use Tempo's reporting surface with all it's functions, but change back all riporting and pre invice data management to sheets.
In case on an issue it is allowed to log with more than one account, this is essential in reporting. Without this we can only use the reporting in the case of 1account/issue, meanning all account related Tempo functions are useless.
Using different accounts under an issue is recommended by tempo documentation.
Raw data export is a very poor workaround, since there is no option to exclude columns from is, just adding custom jira fields, meaning every single time we use it, we have to manually sort and delete 60-70% of its content before it is useable. This also means we do not use Tempo's reporting surface with all it's functions, but change back all riporting and pre invice data management to sheets.