Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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

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

0 votes
Ryan Fish Community Leader Aug 29, 2018

@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.

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. 

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 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

198 views 6 7
Read article

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