title: JIRA issues - 1 task per feature or sub-tasks per individual?
body: <p>We use Jira for issues bugs estimates and timesheets.</p>
  
  <p>I've seen 2 approaches to using Jira and I want to hear what other people are doing.</p>
  
  <p><strong>Approach 1:</strong></p>
  
  <p>Log one feature, such as "Allow user to save as CSV". The task is assigned to a Developer and the workflow progresses from Not started, In Progress, Complete. Once done it's assigned to a Tester and they change workflow to Testing, then to Tested/Completed.</p>
  
  <p><strong>Approach 2:</strong></p>
  
  <p>Log a task/user story called "Allow user to save as CSV". Then developer logs subtasks such as, Front end, Backend and tester logs tasks such as create test plan, test right clicking. Once all dev and test sub-tasks are complete, someone marks the task as completed.</p>
  
  <p>I prefer the first way, I've heard the second way is better for tracking time. It seems harder to manage what's going on with a sea of issues in Jira.</p>