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.
Our cost centers are driven by individuals/teams. Currently, Tempo Accounts are limited to only being tied to Jira Projects. We need the ability to tie Accounts directly to individual users.
this feature is also critical to our client - on Data Center. They want to associate Teams to Accounts to then be able to control what accounts (and budgets) a person is able to log time against.
An account to project only relationship does not work when a project is used by different teams -and thus acconts. Anyone can chose any account on that project and thus can't be restricted to a cost center.
Allowing this level of granularity for Tempo Account associations will result in better integration with our company's use case for timesheets. The current Tempo limitation requires numerous error-prone workarounds.
Christina Wongbuphanimitr Wongbuphanimitr commented
November 22, 2023 20:45
This feature is important for us as well as we are Team funded. Thus accounts (or codes in our case) is associated by individual users vs projects. This limitation to just projects have cause countless hours of waste to fix hours againt the wrong code.
@Tempo - Any chance of you assessing if this is going to be implemented or not?
this feature is also critical to our client - on Data Center. They want to associate Teams to Accounts to then be able to control what accounts (and budgets) a person is able to log time against.
An account to project only relationship does not work when a project is used by different teams -and thus acconts. Anyone can chose any account on that project and thus can't be restricted to a cost center.
We need this for Data Center version.
Allowing this level of granularity for Tempo Account associations will result in better integration with our company's use case for timesheets. The current Tempo limitation requires numerous error-prone workarounds.
This feature is important for us as well as we are Team funded. Thus accounts (or codes in our case) is associated by individual users vs projects. This limitation to just projects have cause countless hours of waste to fix hours againt the wrong code.
In addition to this, being able to tie an account to at least a Tempo Team or other user attribute like role would be really helpful