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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is it possible to break down estimates so that development and testing estimates can be separate?

Rob Horan Community Leader Aug 29, 2018

The development team uses Jira to track their work.  Developers are expected to add estimates to most tickets.  However development time is only part of the overall time to close tickets - QA time is equally important, and in many cases may be much longer than development time.  We would like a way to estimate development and testing time separately rather than chucking it all into a single bucket.  Logging time should be separate so we can track dev vs QA time separately and easily.

2 answers

Curious if you ever found a solution to your problem? We are dealing with the same thing and I have the same complaints about subtasks for all testing needs. 

Rob Horan Community Leader Sep 12, 2019

Nope, the parent company got rid of the team before I got an answer.  Still curious though!

You can add a custom field in Jira, if your admins allow you to.  Mine wont and Im stuck without a solution 

0 votes

@Rob Horan

A simple way to separate QA v dev tasks/ estimates is to use labels and query. The sub-tasks would need to be separate for dev and QA for this to work. Build a dashboard to consume the query data and present based on dev label and qa label.

We thought about this approach and ruled it out long ago. 

The first problem is this would double our ticket set. The second problem is that someone would have to create EVERY ticket for testing.  The third problem is we have dev estimates on subtasks, so then we would need additional subtasks to pair with the existing dev subtasks, which would make management EXTREMELY painful.

Like # people like this

So the more I see how Jira is used (in an Agile, and particularly Scrum manner) the more uncomfortable I am with the number of tickets that get generated.  One little feature could have 10 or more tickets associated with it, stories, tests, etc.  Aie dios mio.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events