Change is required. Atlassian engineer's blog

  Maintaining a clean and efficient Jira installation, especially in an On-Prem setup, involves meticulous data management. A common issue faced by administrators is the duplication of history records for assets in Jira, which can lead to database bloat and performance issues. Duplications often stem from situations such as stuck imports, automated processes running recursively, or incorrect manual imports. This article will guide you through the process of detecting and cleaning up duplicated records, with an emphasis on solutions contributed by the Jira community. Understanding the Issue Duplicated history records can severely impact the performance of your Jira instance. As history records accumulate, database queries slow down, and system memory usage increases disproportionately. In one notable case, duplications reached a staggering 52 million records, prompting an urgent need for cleanup. Detecting Duplicated Records Artem Tumanov, a valuable contributor to the Jira communit...

  Hi!  Today I would like to share just one of the customisations related to the UI. Of course, it's a small AJS, AUI trick :)   Still, most of my Jira instances are DC and Server.  And quite often request to see the standard Log work button on the next panel.  instead of here   That’s easy to set via console log: snippet: const logButton = '<a id="new-log-work" title="Log work" class="aui-button toolbar-trigger issueaction-log-work" href="/secure/CreateWorklog!default.jspa?id='+JIRA.Issue.getIssueId()+'" resolved=""><span class="trigger-label">Log Work</span></a>'; AJS.$('#opsbar-opsbar-operations').append(logButton);    We can set that change into an Announcement  banner  or use some app,  like JSincluder.  You can in marketplace or in github.   Hope it helps. Cheers, Gonchik