title: Best practice for Scrum "done" concept in JIRA
body: <p>I work at a small service based company where we are starting to implement Scrum practices, and we are also starting to use JIRA with greenhopper for issue tracking.  Our team has defined "done" as:</p>
  
  <ul>
  <li>coded</li>
  <li>unit tested</li>
  <li>integration tested </li>
  <li>peer reviewed</li>
  <li>qa tested</li>
  <li>documentation updated</li>
  </ul>
  
  <p>I'm trying to figure out whether this should be done using a separate issue for each item in the above list for each "task", or if some of these items should be implemented in the ticket workflow, or if simply lumping them together in one issue is the best approach.</p>
  
  <p>I'm disinclined to make these subtasks of a task, as there is only one-level nesting of issues and I fear there is a better use for that capability.</p>
  
  <p>I also am not too excited about modifying the workflow, as this approach has proved to be a burden for us in other systems.</p>
  
  <p>If all of these items are part of the same ticket then that seems weird to me because the work is likely spread between multiple team members, and it'll be hard to make tasks that are under 16 hours that include all of those things.</p>
  
  <p>I feel like I understand all of the issues, but as of yet I don't know what the best solution is.</p>
  
  <p>Is there a best practice? Or some strong opinions?</p>