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

Project Management Best Practices for JIRA Core

Hi,

We are a small (but growing) game development studio, and we just started using JIRA, moving our organization from Asana.

Our games are cross-platform, meaning they are released on different platforms (Android, iOS, Web, etc).

Bugs and tasks that go through QA are verified across all supported platforms.

I wonder what would be the best workflow for doing this in JIRA ?

Should we represent the tasks using some kind of custom status until it's completely resolved? should we open (clone) tasks per tested platform ? what could work best here?

1 comment

Peter DeWitt
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 24, 2017

Lior, different Statuses that the bug can transition through would definitely work but it might be hard to track which OS the bug has been QA'd for if you don't test in the same sequence.

You could also create a subtask for each OS and then close them as testing is complete.  

A third idea is to use the rich text editor for the description field (or another) and create a small table that shows the status of testing against each OS.

Comment

Log in or Sign up to comment