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

Version Control File Attachments

XMLWordPrintable

    • 4
    • 8
    • 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.

      Atlassian Update - 22 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      Summary:
      Version Control File Attachments

      Overview:
      I suggest that JIRA should store multiple versions of a file attachment. When users attach a file of the same name as an existing file, the new file is accepted and previous versions stored. Users can download an either version, delete individual versions, or delete the whole file object (all versions).

      Justification:
      Although JIRA may be considered a bug tracking system, it's often used as a Project Managment tool. Our current process defines an elaborate change request process, the outcome of which is a word document. (Personally, I prefer a web form like this!) And, as in so many things, the spec changes 1/2 way through the project. The spec document itself is in some CMS, but we always attach it to the root incident for a project for handy reference.
      Sometimes early decisions can only be explained in context of the previous version of the spec. Having both handy in JIRA would be a time saver. Linking to the CMS is another approach, but there are many version of the document as it changes and before it gets turned over to development.
      Although JIRA is not a replacement for a version control or content management system, this feature request seems to track when JIRA is used to consolidate project information.

      Possible future directions:
      Allow saving a new version with webdav.

      Dependencies:
      In my opinion it's acceptable to require a CVS backend for this functionality. Preferred would be to store in the JIRA tables.

      Thanks,
      Darren.

              Unassigned Unassigned
              7fce57957272 Darren Gilroy
              Votes:
              202 Vote for this issue
              Watchers:
              107 Start watching this issue

                Created:
                Updated: