kumo and Jira
What a studio uses Jira for, where it lives in kumo, and what stays different.
Jira, in its own words
Atlassian presents Jira as a place where teams and agents turn ideas into tracked work: intake from chat, planning, hand-off and review, with its Rovo assistant.
From Atlassian's page, read on 18 October 2026.
Where that work lives in kumo
- The backlog, sprints and the board Plan & produce
- Bugs and QA Bugs & QA
- Roadmaps and milestones Plan & produce
- Automations on issues Plan & produce
What Jira does that kumo does not
- Atlassian's marketplace of apps and its many enterprise add-ons.
- Deep ties to the rest of the Atlassian suite (Confluence, Bitbucket, Jira Service Management).
- Years of large-company administration: complex schemes, many projects, very large instances.
What kumo adds
- Bugs that know their build, crashes grouped into bugs, and an in-game reporter.
- Frame-accurate review of art, video, 3D and sound on the task.
- Builds, store pages and releases beside the work.
- A concept-first wiki, boards, HR and funding in the same app.
Moving over
kumo imports Jira projects and stays in sync with them both ways, comments included, so a team can move at its own pace.