How do you differentiate between Dev and QA activities/issues?

What's the best method to differentiate between Dev & QA issues/activites? We could use custom issue types, tags, or custom fields. What works for other people?

1 answer

1 accepted

3 votes
Answer accepted

I like to use different types of subtasks

Good thinking. Thanks.

So dev, qa, general sub-tasks and tasks makes sense. Are you then able to derive Dev/QA capacity/allocation off of those?

yes... and it also allows you to fold in things like code reviews (whether or not you use Crucible - but its easier with) and even design if you need. There are a number of different ways to set it up, but I prefer everything to roll up nicely into a single issue when possible so you can see exaclty how long a feature took to build (including testing and design), and where in the process it is.

Like 1 person likes this
Deleted user Sep 10, 2011


This is interesting. Can you please elaborate more on this? I mean, the complete process?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

641 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you