Blog ·

Jira for game development: playtests, bugs and live ops

Jira for game development works best when it carries three kinds of work at once: the milestone work that builds the game, the bugs QA finds in every build, and the recurring calendar that a game in production or live operation runs on. Most studios set up the first two well. The third, the weekly playtest, the build certification pass, the seasonal event and the monthly platform patch, usually lives in a producer's head and a shared spreadsheet. This guide covers how to structure all three, and spends extra time on the calendar, because that is where a small team loses days.

Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation.

What a game team needs from Jira #

A studio asks different things of Jira at different stages of a project, and the board should reflect which stage you are in:

Stage The work that dominates What Jira should do
Pre-production Prototypes, design docs, vertical slice Hold a short backlog of experiments with clear owners
Production Features, content, art and audio assets Track work per milestone, across disciplines
Alpha to certification Bugs, polish, platform requirements Route bugs fast and show what blocks the build
Live operations Events, patches, balance updates, store refreshes Create the recurring work on time, every cycle

The last row is the one Jira does nothing about by default. Feature work gets tickets because a producer planned it. Bugs get tickets because QA filed them. A seasonal event that needs art, a store listing and a balance pass three weeks before it goes live gets a ticket only when somebody remembers the date.

Set up the projects #

There are two common shapes, and both work.

  1. One project for the whole game, with components for each discipline (design, engineering, art, audio, QA, UI) and a fix version per milestone. This is the simpler choice for a team under about 30 people, because everyone reads one board and dependencies between disciplines stay visible.
  2. One project per discipline, plus a production project that holds the milestone epics. Larger studios choose this because each discipline wants its own workflow: art has concept, model, texture and review stages that engineering does not.

Whichever you pick, use epics for features ("Crafting system", "Chapter 3 levels") and fix versions for milestones ("Vertical slice", "Alpha", "Beta", "Gold"). A fix version answers the question producers ask most: what is still open for the next milestone? Our Jira epic template guide shows what to put in an epic so every feature starts with the same fields.

A workflow for assets #

Art and audio move through review stages that a plain "To do, In progress, Done" flow hides. A workflow that matches how assets are made:

Status What it means
Brief Reference and requirements agreed
In progress The artist or designer is working on it
Review Waiting on the art director or lead
Changes requested Back to the author with notes
In engine Imported and checked in a build
Done Approved in context

"In engine" is the status teams most often skip, and it is where problems show up. An asset that looked right in the authoring tool can be the wrong scale, the wrong colour space or too heavy for the target platform. More examples are in Jira workflow examples.

A bug flow QA can live with #

During alpha and beta, bugs outnumber every other work type. A few fields make the difference between a bug database the team trusts and one it ignores:

Then build two saved filters and put them on the dashboard: open crashes and blockers for the current milestone, and bugs marked fixed but not yet verified by QA on a newer build. The second one is the filter that stops a "fixed" bug from shipping. Our Jira QA testing guide covers test cycles and the regression routine in more depth, and Jira dashboard examples shows layouts that work for a lead's morning check.

The recurring calendar of a game team #

This is the routine most studios carry once a game is in production. Every row is work that happens whether or not a ticket exists:

Recurring work Typical cadence What goes wrong without a ticket
Internal playtest Weekly Feedback is gathered informally and lost
Build health and smoke test Daily or every build A broken build sits for a day before anyone notices
Milestone build review Every milestone Scope creep reaches the deadline unseen
Platform requirements pass Before each submission A certification failure costs a resubmission
Live event preparation Per season or monthly Art and store copy are late for the launch date
Balance and economy review Every two weeks in live ops Players find the exploit first
Store page and screenshot refresh Quarterly The store shows features the game no longer has
Crash report triage Weekly Top crashes stay top crashes
Engine and SDK update review Quarterly An update becomes a forced migration
Community feedback digest Weekly The same request arrives for months unanswered

Each item is small, and that is why it slips during crunch. A recurring item with a ticket has an owner, a due date and a record that it happened. One without depends on the producer remembering it in the week they have the least room to.

The record has a second use. When a publisher or platform holder asks whether crash reports are reviewed every week, a filter showing a year of resolved triage tickets, each with notes, is the answer.

Live events need a lead time #

A live event is the case where the date matters most. If a winter event goes live on the first of December, the work starts weeks earlier: event art, store copy, a balance pass and a QA sweep. Create the ticket on the lead date, not on the launch date. A recurring rule that creates "Winter event prep" on the first of November with a due date thirty days out gives the team the whole month, every year, without anyone checking a calendar.

Three ways to create the recurring tickets #

Clone by hand Jira Automation scheduled rule A scheduling app
Who creates the ticket A producer, every cycle A rule A rule in the project
Setup per item None A rule, often with a cron expression A rule, in a form
"Last Friday of the month" Whoever remembers Needs cron Chosen in the form
Studio holidays and shutdowns Whoever notices Handled in the rule's logic, if at all Set once for the project
During crunch Often skipped Created on time Created on time
Cost Producer time Counts toward your plan's automation usage App licence

Clone by hand #

Keep a master ticket for each recurring item, with the checklist in the description, and clone it each cycle. It costs nothing and suits a small team with a handful of routines and one disciplined producer. It breaks during crunch, which is exactly when the weekly playtest matters most.

A Jira Automation scheduled rule #

Atlassian's trigger reference, as of October 2026, says a scheduled trigger can "run the flow at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules." A weekly playtest is a simple rule. "The last Friday of every month" or "every second Wednesday" needs cron, which our Jira cron expression guide explains, including the schedules cron cannot express.

Two points before you build a dozen of these. Every run counts toward your plan's automation usage, which Jira Automation pricing explains. And the same Atlassian page says:

Scheduled flows that reach a Failure status for 10 consecutive executions will disable automatically.

For a quarterly store refresh that is years of failures, and then a rule that is quietly off. If you use Automation, put "check the automation audit log" on the list.

A scheduling app #

Recurring Work Items for Jira is our app, and recurring routine work is the job it was built for. A studio routine becomes a rule in the project:

  1. Turn the app on for the game's project and choose who may schedule.
  2. Set the working week and add studio holidays and shutdown weeks, so a rule can move off a day nobody is in.
  3. Create a rule per routine. The options are every N days, chosen weekdays every N weeks, a day of the month every N months, or a weekday position such as the second Tuesday or the last Friday of the month.
  4. Name each ticket with tokens, for example Playtest {{now.date}}, so every cycle has its own title in search.
  5. Put the checklist in the description or as subtasks, and set the assignee, components, labels and a due date as an offset from the run.

It uses no Jira Automation quota, because the scheduling is the app's own. Every created or failed run is written to the rule's history with its reason, so "why is there no crash triage ticket this week?" has an answer. A rule is scoped to the one project it lives in, so the game team's schedules never create tickets in another team's project. It is free for up to 10 users.

A starter set of studio rules #

Adjust the cadence to your own production. Add a routine label to every rule so the filters can find them.

For routines with several fixed steps owned by different people, use subtasks rather than one long description. See Jira subtask template and Jira release checklist, which applies directly to a patch.

When the manual way is enough #

If the team is a handful of people and one producer owns every routine without fail, a calendar reminder and a cloned ticket are enough. If your cadences fit a fixed rate and your Automation usage has room, a scheduled rule for the weekly playtest is the natural next step. A scheduling app earns its place when the routine list grows past what anyone wants to maintain as cron, when shutdown weeks keep producing tickets nobody will work, or when a publisher wants proof that each cycle happened.

For a wider view of the options, see Jira recurring tasks, and for running sprints on a feature team, Jira sprint planning.

Frequently asked questions #

Is Jira good for game development? It is a common choice for studios once a team grows past a few people, because it handles milestones, cross-discipline dependencies and high bug volume in one place. Very small teams often find a simpler board enough.

How should a game studio structure Jira projects? One project with components per discipline suits most teams under about 30 people. Larger studios often run a project per discipline plus a production project for milestone epics.

How do I schedule recurring playtests in Jira? Clone a master ticket each week, create a Jira Automation scheduled rule, or use a scheduling app such as Recurring Work Items for Jira, where "every Thursday" or "last Friday of the month" is chosen in a form.