Content
Document Revisions: Best Practices
Added by rod boggess over 3 years ago
How do you guys handle revisions to an existing project document? Do you just delete older revisions, leaving document control to another tool, or do you create a second copy of the same document?
I keep looking for an option in here that will allow me to define a relationship between two documents that makes one the predecessor to the other. It'd be awesome if I could establish a relationship between two documents such that, when you established a revision relationship, you only had to see the most recent version of a document listed on the main documents page (with a revision count), but clicking on the document allowed you to navigate to previous revisions.
It's nice to be able to see the progression of software requirements, in particular. I feel like I'm missing something.
Replies (3)
We also have difficulties to manage documents attached to work packages. As the search for work packages with documents attached is not useful and there is no preview in OP, we use a third party software for document management. OP is not a tool for document management but u'r right, it can be better than today to manage a project in full details.
Hi Rod, hi Rainer,
we're working on an integration. Stay tuned for updates.
Kind regards
Hi Rod,
you could use the wiki for this. For every wiki page there's a history available, and you can also leave comments when changing the wiki page. Furthermore, this would allow you to link resources in OpenProject (work packages, people, etc.).
For our documentation we use GitHub.
Generally speaking, managing documents is not the focus of OpenProject. However, stay tuned as we're working on something as I mentioned earlier.
Kind regards