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.