We are using Tempo Timesheets 7.11 and recently experienced a scenario where an issue with worked logged to it was deleted after that user's timesheet had been approved. As a result, the approved timesheet now shows less hours than when it was approved. Is there a way to prevent this without completing restricting the ability to delete issues?
@Jobin Kuruvilla [Go2Group] is correct, it is not recommended to delete Issues for this very reason. JIRA Worklogs are tied to Issues and if an issue is deleted, the worklogs will be as well. This is simply how JIRA works in the back. I'm interested to know why you would need to delete an issue, especially one that has work logged on it. Best regards, Albert Hauksson Tempo Team
Thanks for the reply. The issue in question was inadvertently deleted. I wanted to verify whether there was a way to prevent deletion of issues that had worked logged. In some cases for us it is helpful for Project Leads to delete unnecessary issues that are not used for logging work. We have removed delete permissions for all issues and we'll just close these issues when that situation arises.
We recently ran into a similar problem where someone didn't realize that an issue was being used to track time (tagged as an internal issue in Tempo). Is there a way to specify that Internal issues can't be deleted? I'd prefer not to turn off the ability to delete items globally just to prevent this problem. Is there anything that can be done from the Tempo side?
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs