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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,457,938
Community Members
 
Community Events
176
Community Groups

Managing multiple skillsets

In our application workflow, we have two distinct phases - development and QA testing.  I currently have a single project in JIRA, which works great for a developer - tracking their hours estimated versus actual, all the usual good project management stuff.  However, while development is going on, I also have QA Analysts booking time to script out their tests, and ultimately they will take over the issue for testing.

I don't want QA and Development hours (estimated or actual) being mingled because that makes it almost impossible to track development progress.  However, I also don't like creating a "QA Subtask" for each development task because now you have two cards to move through the process.

I'm sure (I hope) I'm not the only one with this challenge - how are you managing this sort of situation with JIRA?  Currently "just" JIRA cloud - open to addons if needed.

Thanks!

0 comments

Comment

Log in or Sign up to comment