We have different parts of the organization that use Tempo in different ways. One part of the organization (comprised of several Teams) requires the Account attribute on every worklog, the other part of the organization doesn't use Accounts at all.
Currently, we have Account worklog attribute added, but the implementation is far from perfect because:
since 50% of the organization doesn't use Account, we cannot mark it as required
the log work screen, by default, doesn't display the added Account field (you have to click a link to expand the form in order to see it)
The above lead us to have a LOT of worklogs entered without the Account populated which diminishes the usefulness of Tempo.
The ideal scenario would be to be able to add worklog attributes (Account, in particular) scoped to specific Teams (or Projects) and make it required in that scope. A less ideal alternative would be to keep the Account worklog attribute global, but allow defining default values per team (this way, we can make the attribute globally required, but have a default value for the team which doesn't use Account).
Without the above feature, I feel pretty strongly that Tempo would not be a viable solutions for larger organizations that have groups with different needs.
Tempo Products | Tempo Timesheets |
Tempo Platform | Cloud |
This is our exact situation as well and having Tempo implement this would be of great value to our organization as well.