Jira ticket "buckets" can sometimes have hundreds of entries per ticket when dealing with items like PTO and company wide meetings or system outage. When entering time against these larger buckets jira becomes unresponsive or very slow. Any solutions other than creating new buckets?
See this community article that was published after Atlassian introduced limitations, e.g. on the maximum number of worklogs on an issue exactly to address these performance issues.
While I think creating new issues (buckets) regularly is the easiest solution, the article also mentions a couple of alternatives.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.