When an existing work log is updated with a different issue key, the original Account is retained even if it is unavailable in the newly selected issue's project. The user would instead like either an option to disable the existing behaviour or at least warn that the account is no longer available for the selected issue.
Tempo Products | Tempo Timesheets |
Tempo Platform | Cloud |
+1 this is a major issue for us as well, I am wasting a lot of time "cleaning up" wrong accounts when users are booking time this way.
+1, please implement some guardrails to prevent users from booking on accounts not associated with a given project. This is a very unintuitive and risky behaviour. Thank you.
We spend at least 1 man-day every month correcting the problems cause by this logic in Tempo. Users often change the logs (and it's reasonable user behaviour), sometimes transferring hours from one project to another. Due to the current logic in Tempo, the account field remains the same, and it results in messy data where some projects end up in the wrong accounts (that have never been associated with these projects). We have to clean the data every month. It's an unnecessary effort and really not through-through logic from Tempo. Please, either advise users that they need to change the account or forbid to save the edit if the selected account is actually not linked with the project.
This is a major issue for us, as it allows individual users to circumvent the rules we have around which Accounts are available in each Project.
We end up with a scenario where people have time logged in a Project against a random unconnected Account.