Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-29380

Option to store attachments in the database

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Currently, JIRA only stores attachments on the file system. This creates an issue with backup and recovery. While both can be backed up using whatever means determined by the user, the back up for the file system is only good at the point when the backup occurs. Since it is next to impossible to match the database and file system backups up, restoration can be miss matched. This is especially true when the database exists on a separate server as is the case in most larger environments. If the attachments could be stored in the database, the inconsistencies exist in the file system/database backups would not exist.

      The other positive to storing the attachments in the database is the database can be restored to any given point in time. Since Jira is very dynamic and data is constantly changing and/or being added, this capability minimizes data loss.

            [JRASERVER-29380] Option to store attachments in the database

            Irving Neil Kwok added a comment -

            I was taken aback to find that this is still not an option in the newest JIRA 6.0 given that this is available in Confluence.

            Irving Neil Kwok added a comment - I was taken aback to find that this is still not an option in the newest JIRA 6.0 given that this is available in Confluence.

            Lorraine Todd added a comment -

            This really needs to happen. I do not understand how it is viable on Confluence but not on Jira. Surely it is just a few tweaks to the Confluence code to store and retrieve the images.

            Lorraine Todd added a comment - This really needs to happen. I do not understand how it is viable on Confluence but not on Jira. Surely it is just a few tweaks to the Confluence code to store and retrieve the images.

            Steven Teleki added a comment -

            Confluence has been able to do this for a while now. Could somebody just lift the code from Confluence and make it happen on Jira, too?

            +1 for "If the attachments could be stored in the database, the inconsistencies that exist in the file system/database backups would not exist."

            Steven Teleki added a comment - Confluence has been able to do this for a while now. Could somebody just lift the code from Confluence and make it happen on Jira, too? +1 for "If the attachments could be stored in the database, the inconsistencies that exist in the file system/database backups would not exist."

            Craig Oliver added a comment - - edited

            Duplicate of JRA-806, which was closed (won't fix) last year. Perhaps its time to revisit and reconsider. There are valid operational reasons to store attachments in an Enterprise Database along with the associated issue data. One of the major reasons is to allow a warm standby instance of JIRA, where the data in the database is continually replicated to a different location.

            (edit - fix issue link)

            Craig Oliver added a comment - - edited Duplicate of JRA-806 , which was closed (won't fix) last year. Perhaps its time to revisit and reconsider. There are valid operational reasons to store attachments in an Enterprise Database along with the associated issue data. One of the major reasons is to allow a warm standby instance of JIRA, where the data in the database is continually replicated to a different location. (edit - fix issue link)

              Unassigned Unassigned
              e73ecf029b7c John Rich
              Votes:
              4 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: