Jira for Unreal Engine

What it is

Jira organizes work into work items such as tasks, bugs, stories, and epics. Teams configure statuses and transitions, then view the same work through backlogs, boards, filters, and release plans.

Jira lets a studio give animation requests and certification bugs different fields and approval steps. Shared workflows help departments agree on what a status means, but someone needs to maintain that configuration.

Start with a bug workflow such as Open, In Progress, Ready for Test, and Done. Add a status when it changes who acts next or what they need to check.

With Unreal Engine

A studio can track bugs, department handoffs, milestones, and releases in Jira. For example, an inventory bug can move from Open to In Progress, then wait for a playable-build check before it reaches Done.

Where it fits

How it works

Work types and fields

Work items, commonly called Jira issues, include tasks, bugs, stories, epics, and custom types with different fields. A crash might need platform, build, call stack, and reproduction steps. An animation request does not. Every required field needs a reason to exist.²

Workflows

A workflow defines statuses and transitions. Conditions and validators control who can move an item and what information is required. If two statuses have the same owner and next action, it's ideal to combine them.³

Boards, backlogs, and JQL

Scrum and Kanban boards are views over work selected by filters. JQL gives those filters a query language for fields, dates, users, versions, and relationships. One item can appear in several useful views without being copied.¹

Releases and development data

Versions collect work planned for a release. A 0.6.2 version can show which bugs are open, in progress, or done before the build is cut. Connected development tools can also place commits, pull requests, builds, and deployments beside the work item.⁴

Automation flows

Automation flows use triggers, conditions, and actions to update work. The audit log records each run. Atlassian now documents usage in executed steps pooled across the organization, separately from per-execution service limits.⁵⁶¹²¹³

In production

1. 01

   Model the work before configuring Jira

   Write down each handoff and the evidence it needs. A Ready for Test status can require a build number and reproduction steps before QA takes over.

2. 02

   Create views for decisions

   Make the daily board answer what is active and blocked. Make the 0.6.2 release view answer what still prevents the build. If a field does not change either decision, it does not belong on that view.

3. 03

   Attach evidence to the work

   Put the build number, review link, crash report, or pull request on the item that needs it. "Fixed" is not enough for the inventory focus bug. QA needs to know which build contains the change and what action reproduces it.

4. 04

   Automate narrow, repetitive changes

   Use automation for mechanical updates such as assignment, field synchronization, or reminders. Give each flow an owner, test it with a manual trigger, and review its audit log. A flow with a broad query can change hundreds of work items in one run.

5. 05

   Remove fields and workflows nobody uses

   Review unused fields, stalled work, failed automation, and permission problems. Remove requirements that don't help someone route or finish the task.

Best practices

Choose the management model first

Use a team-managed space when one team needs local control and a company-managed space when several spaces must share workflows, screens, fields, and permissions. Changing a shared scheme can affect every company-managed space that uses it.²

Keep statuses tied to decisions

Use a transition only when the owner, allowed action, or evidence requirement changes. Where the workflow has a Resolution field, set it on terminal transitions and clear it when work reopens. Service team-managed spaces use the Done status category instead.¹⁰¹¹

Limit field scope and obligation

Give each required field a routing, reporting, or compliance use. Restrict custom-field contexts to the work types and spaces that need them instead of placing every field on every screen.

Give each automation flow an owner

Give each flow an owner, narrow its query, test permissions through the rule actor, and inspect the audit log after changes. Watch service-limit warnings and use bulk operations for large one-time edits.

Export the parts Jira does not protect for you

Schedule a Jira data backup with attachments, then export automation flows and document Marketplace app recovery separately. Restore into a safe target before claiming the backup plan works.

Gotchas

One scheme change reaches every space using it

A workflow, screen, or field change in a company-managed scheme can alter several spaces at once. Clone and test the configuration or use a draft before publishing it to active work.

Plan dependencies need Premium or Enterprise

Dependency views in Jira plans are part of the advanced planning features on Jira Cloud Premium and Enterprise. Dependencies also read every work item link as a Blocks relationship until an administrator maps the link types the team actually uses.⁹

Done status and Resolution are separate

In workflows with a Resolution field, a work item can appear Done while Resolution remains empty or carry a resolution after reopening. That breaks unresolved filters and reports until transitions set and clear the field. Service team-managed spaces use the Done status category instead.¹⁰¹¹

Automation usage is measured in steps

Atlassian has replaced its published per-app run allowances with organization-wide automation steps. Executed triggers, conditions, actions, branches, and loops count toward usage. Check Platform usage in Atlassian Administration for the allowance and overage controls that apply to your organization.⁶¹²¹³

Cloud backups omit automation and app data

Jira Cloud exports omit automation flows, Marketplace apps and their data, and several product-specific stores. Backups that include attachments also need 48 hours between runs.⁸

The audit log can't restore deleted data

It can show who deleted a work item or changed configuration, but deleted data still needs a backup or export for recovery. Audit visibility also depends on plan and administrator permission.⁷⁸

Adoption checklist

• Name each status after a real state, not a department or meeting.
• Keep required fields to the minimum needed for routing, reporting, or compliance.
• Assign owners for global workflows, fields, automation, permissions, and integrations.
• Separate release versions from sprints and short planning periods.
• Test what artists, contractors, leads, and external partners can see and edit.
• Audit failed automation and stale work instead of adding more reminder rules.

Related guides

• Project FeedProject management with built-in file review.
• LinearIssue tracking with projects, milestones, optional cycles, and GitHub or GitLab links.
• GitHub ProjectsTables, boards, and roadmaps built from GitHub issues and pull requests.
• Frame.ioFile review with timecoded comments, version comparison, share links, and supported 3D previews.
• SyncSketchSynchronized review for animation dailies, drawovers, audio, and supported 3D files.

Sources

Official sources checked September 24, 2026.

1. 1Configure Jira boardssupport.atlassian.com
2. 2Jira space management typessupport.atlassian.com
3. 3Jira workflowssupport.atlassian.com
4. 4Jira releases and versionssupport.atlassian.com
5. 5Jira automation flowssupport.atlassian.com
6. 6Jira automation limitssupport.atlassian.com
7. 7Jira audit logsupport.atlassian.com
8. 8Jira cloud exportssupport.atlassian.com
9. 9Jira plan dependenciessupport.atlassian.com
10. 10Configure resolutionssupport.atlassian.com
11. 11Resolution in service team-managed spacessupport.atlassian.com
12. 12Automation audit logsupport.atlassian.com
13. 13Automation usage limitssupport.atlassian.com