CODEWITHSUNDEEP
jira
ProgrammerGuy
ProgrammerGuy

Reputation: 439

JIRA issues - 1 task per feature or sub-tasks per individual?

We use Jira for issues bugs estimates and timesheets.

I've seen 2 approaches to using Jira and I want to hear what other people are doing.

Approach 1:

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.

Approach 2:

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.

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.

Upvotes: 1

Views: 211

Answers (2)

mdoar
mdoar

Reputation: 6881

I recommend using sub-tasks when you need to have work proceed in parallel. Or if the parent task is really large and the sub-tasks are around a few days each. But don't create sub-tasks unless they are needed.

Upvotes: 1

Arthur Swails
Arthur Swails

Reputation: 179

My company does first approach. This seems to be working so far ( about a year now ). With either approach I really love how everything seems to be logged in JIRA for history tracking.

Upvotes: 1

Related Questions