Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA for repetitive document production management

I am considering using JIRA to monitor and manage a bulk document review and correction process.

This may be a process that has some similarities to other repetitive processes for totally different purposes than document review and correction so please read on.

This is a single project that involves aproximately 10,000 property deeds that will be reviewed by a team of 10 analysts over a period of 100 working days. Each review follows a preset process involving aproximately 10 steps which are not completed at one sitting. So even though on average 10 documents a day per analyst are produced an analyst will be pausing work on documents at the completion of specific steps and returning to documents while waiting for additional information. So analysts may be working on many more than 10 documents in a day.

Any thoughts on the applicability of JIRA to this requirement?

Is any one actually using JIRA to monitor and manage a bulk document review and correction process?

2 answers

Hi Joel,

JIRA is opened for different customisations you mentioned. But without further workflow info - it's impossible helping you out. We might find some solution for sure, contact with our Atlassian team via -


1 vote

Yes, I know of a few places doing something like this. There are two things you need to do

1. Identify each discrete step in the process so that you can convert it into a "status" in a Jira workflow. If, for example, you've got a document that arrives, gets edited by an author, then needs to out to a client for checking, then cycles between author and client, and eventually gets signed off, you probably want a workflow based on "New", "With Author", "With Client", "Signed off". The trick here is to have status that clearly indicates where the task is.

2. Make a clear link between tasks and the things that need doing to documents. The last place I saw something like this, they had one issue per document, but then created a sub-task for each individual piece of review that needed doing (e.g. "chapter 4 doesn't look right" or "appendices are all wrong")

There are quite a lot of variations and tricks you can do here, and Jira can help you a lot. But you'll need to analyse your needs.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you