We have been experiencing lagging and locking issues that we were advised is linked to our practice of having "bucket" tickets that are used year-over-year for overhead work logs.
We do need to report on some of this time historically and have since enacted policies to create new tickets each year for these activities - but how do we keep the existing tickets/worklogs from continuing to cause issues? We do not have the capacity to move these worklogs one at a time to new tickets.
We would like to be able to bulk move the worklogs by year to new tickets for those years where we cannot delete the worklogs.
Is it possible to archive a portion of the worklogs? or will we have to archive the whole tickets? Is it possible to make archived worklogs available for reporting but not need to be indexed constantly?
If you are on Data Center and have something like ScriptRunner, this is possible with a script, lots of testing in non-prod and some exploratory coding. A quick google of "jira bulk move worklogs" suggests that the Tempo plugin will also do this in Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.