Using Atlassian Tools for Document Control

[aadams]

I'm looking into tools to use for document control for a software development project. (Well, I'm researching software development tools like the Atlassian products in general, but document control is part of my interest.)

I'm the CM analyst/tools expert for the project.

By documents, I mean existing files, mostly Microsoft Office. They're all related to the project, but not all will be directly related to software development. For instance, we'll have requirements documents, and those are directly related to development. But we'll also have things like plan and process documents, contract-related files, schedules -- the type of documents that will not be associated with commits to our code repository.

We need to store the documents hierarchically, and related to that, we need to show the dependencies in documents -- for instance, we need to show that in one document is changed, another one might need to change, too.

I think bitbucket will at least allow that somewhat, but I am very much unsuppportive of using source code control tools for document management. That's largely from some bad experiences being forced to use Subversion for document control; perhaps Bitbucket, with git or Mercurial underlying it, will be better, but I tend to suspect not. My main concern is having non-developers use such a tool; I've found in the past that it was a stumbling block. Disk space is a concern, too, but that's mainly from experience nearly a decade ago when disk space was more expensive and the project I was on wasted a lot of space on a svn repository for documents. (Raw audio files of meetings...)

I know Microsoft SharePoint is something of a solution, but our customer has issues with it.

So, to summarize, I need

1. A document management system
2. To show relationships between documents.
   1. That includes dependencies between documents "if process A changes, procedure B needs to change to reflect it."
3. To track work and issues related to those documents
   1. For instance, "Mary needs to update the overall Test Procedure document"
4. To associate source code commits with documents
   1. For instance, show that a commit was related to a given requirement document
   2. That should be in addition to the normal commit comments, not instead of
5. To associate developers' issues with documents
   1. For instance, "Bob is responsible for the code changes described in this requirement"

[Aron Gombas _Midori_]

This is interesting.

Questions:

1. How would you associate the document (Confluence page) with a code commit?
2. And how would you associate a developer (or his/her issues) with a document?

[MattS]

Confluence should work for most of those. Showing relationships might be helped by an add-on though. I'd link commits with JIRA issues and then show the JIRA issues in Confluence pages