We have several 'internal' type tickets for recording time, using Tempo. We'd like to make some changes to these.
I would like to close and delete six of these tickets in order to replace the six with one ticket.
The sticking point is the moving of the existing worklogs from the old tickets to the new ones. It can be done manually for each worklog in the web interface, but I may be looking at hundreds (or more!) of entries.
I'd be happy doing this at the database level (using MySQL), but I want to be sure it is safe. Can someone confirm the best process to acheive this?
you can use MySQL, but it is not without risk and not supported. The table in the Database is "Worklog" and you should make sure to stop your server before making changes to the Database.
It might be easier to create the new Internal issue and include the old ones there as subtasks instead of deleting them.
This is not supported in our current Tempo Timesheets version, but you can create a feature request in our Atlassian JIRA (https://tempoplugin.jira.com/browse/TT).
Other users with similar requests can vote on these issues and contribute by adding comments that will help Tempo developers implement the request.
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
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