Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

General discussion
  1. OpenProject
  2. Forums
  3. General discussion
  4. Document Revisions: Best Practices

Document Revisions: Best Practices

Added by rod boggess about 4 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)

RE: Document Revisions: Best Practices - Added by Rainer Proehl about 4 years ago

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.

RE: Document Revisions: Best Practices - Added by Max Mutzge about 4 years ago

Hi Rod, hi Rainer,

we're working on an integration. Stay tuned for updates. 

Kind regards

RE: Document Revisions: Best Practices - Added by Max Mutzge about 4 years ago

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

  • (1 - 3/3)
Loading...