Automated Archiving Tool for Jira Database Stability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current defect-tracking platforms like Jira lack a mechanism for efficiently removing historical issues, leading to software platform instability, increased maintenance costs, and reduced database access times due to accumulated obsolete records, which hinders historical reporting and audit traceability.
Innovation Solution
An automated archiving tool that queries for issues meeting specific criteria, exports them, creates macros for tickets and attachments, archives as flat files, indexes by project, moves support files, and identifies local references, allowing for the removal of entries from the database while maintaining historical records.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If historical issues are retained in the database, then historical reporting and audit traceability are maintained, but software platform stability deteriorates and database access times increase
Solution Approach 1:
The patent segments historical issues into two categories: active issues remaining in the Jira database and archived issues stored as flat files. The archiving tool queries for issues meeting archive criteria (e.g., closed status, age thresholds), exports them to HTML flat files with associated attachments, and removes them from the database. This segmentation maintains platform stability by reducing database burden while preserving historical records externally for reporting and audit purposes.
Solution Approach 2:
The patent extracts historical issues from the Jira database and stores them in an external archive format. The archiving tool identifies candidates for archiving, exports them as flat files with all associated attachments and metadata, and removes them from the active database. This extraction eliminates the harmful accumulation of obsolete records while maintaining access to historical data through the flat file archive, resolving the contradiction between database performance and historical record availability.
2Productivity
If historical issues are deleted from the database, then database access times improve and maintenance costs decrease, but historical reporting and audit traceability are compromised
Solution Approach 1:
The patent performs preliminary archiving before deletion by querying for issues meeting archive criteria, exporting them to flat files with complete metadata and attachments, and verifying successful export. Only after this preliminary action is confirmed does the system remove the issues from the database. This ensures historical data is preserved in the archive before deletion, maintaining both fast database access times and historical reporting capability.
Solution Approach 2:
The patent creates a copy of historical issues in flat file format with all attachments and metadata before removing them from the database. The archiving tool exports selected issues as HTML flat files that contain complete issue data, descriptions, comments, and embedded attachments. This copying process preserves historical information externally, enabling fast database access for active issues while maintaining historical reporting and audit traceability through the flat file copies.
3Loss of information
If additional Jira instances are created for archiving, then historical record preservation is achieved, but device complexity and maintenance requirements increase
Solution Approach 1:
The patent uses a simple flat file format for archiving instead of maintaining complex additional Jira instances. Historical issues are exported to lightweight HTML flat files with associated attachments stored in a file system. This disposable archive format requires no additional database infrastructure, instance management, or complex system architecture, yet effectively preserves historical records for reporting and audit purposes.
Solution Approach 2:
The patent introduces a flat file archive as an intermediary between the Jira database and historical record requirements. Instead of creating additional Jira instances, the system uses simple text-based flat files as a mediator to store and preserve historical issue data. This intermediary approach simplifies the system architecture by avoiding the complexity of multiple database instances while maintaining historical record preservation capability.
Data Source
AI summary
An embodiment of the present invention is directed to an automated archiving tool. A system that implements an automated archiving tool comprises: a memory component; an interactive interface that receives one or more user inputs; and a processor, coupled to the memory component and the interactive interface, the processor configured to perform the steps comprising: querying for issues that meet an archive criteria; performing an export of the queried issues that meet the archive criteria; executing a script creating a macro for tickets and associated attachments; archiving the tickets as flat files; executing a script to index the archived issues by project; moving support files to a common directory; macro archiving the attachments; and identifying local references.