We are still on Jira Server, migration stuck
A Server instance that is out of support, Marketplace apps that are no longer sold for Server, and a migration project that started twice and never finished.
On Cloud with history and structure intact
Running Jira?
Jira collects complexity the way old houses collect wiring. A workflow with a transition nobody understands, a custom field used by three teams with three meanings, an automation rule firing in a loop since 2021. We go through the project structure, the schemes and the automations and leave you with something a new hire can actually read.
What it is
Jira is Atlassian's issue tracker, launched in 2002 and now the default project management system across a huge share of software teams. It covers agile boards (Scrum, Kanban), classic project management, service management (Jira Service Management), and work management for non-engineering teams.
The deployment landscape has shifted hard toward Jira Cloud. Jira Server reached end of life in 2024, Data Center continues for larger self-managed customers, and Cloud is now where Atlassian invests. Most of the work we see is cloud migrations from aging Server instances, workflow simplification on inherited instances, and automation rules that have grown past what the team that built them can still debug.
The honest version
No technology is all upside. This is where Jira earns its place and where it tends to cause trouble.
Sound familiar?
The Jira problems that bring people to us, and what you have once each one is fixed.
A Server instance that is out of support, Marketplace apps that are no longer sold for Server, and a migration project that started twice and never finished.
On Cloud with history and structure intact
A rule that edits a field that re-triggers the rule, or two rules on the same issue that trigger each other, eating the monthly automation quota and spamming history.
Rules de-looped and metered
A filter written against custom fields that were renamed or deleted, or JQL syntax that differs subtly between Server and Cloud after a migration.
Filters rewritten against current schema
A transition validator that requires a field most users cannot see, or a condition that depends on a project role nobody is in, so issues get stuck in a status.
Transitions passable by the right people
Hundreds of custom fields, half with similar names, used by different projects for different purposes, slowing the UI and confusing reports.
Custom field inventory rationalized
A legacy export with usernames that no longer exist in the target directory, or with email addresses from a domain that was retired.
User mapping prepared before import
A permission scheme edit that removed Browse Projects for a role, or a project moved under a scheme that assumed different group memberships.
Permission schemes audited and fixed
Cloud migration that left one tool on Cloud and the other on Server, or application access settings that no longer grant cross-product permissions after a license change.
Cross-product access reconciled
What we do
Call us for one bad workflow, or hand us the entire Jira instance.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. Server is out of support and Data Center is the alternative if you have a reason to stay self-managed. For most teams the move is to Cloud. We run the migration in stages: audit of custom fields and apps, Marketplace app compatibility check, test migration on a sandbox, user and group reconciliation, and finally the production cutover with a rollback plan.
Because something it changed re-triggers the rule, or another rule is acting on the same issue and the two chase each other. The fix is to narrow trigger conditions, use the 're-fetch issue' step rather than editing in place where possible, and watch the monthly automation usage so the first loop gets caught before the quota does.
Inventory first: which fields are used on which screens, which are populated, which are referenced in JQL and automation. Then consolidate duplicates, retire the unused ones, and lock down who can create new fields going forward. A clean field schema makes everything from reports to dashboards noticeably faster on Cloud.
A validator or condition on the transition is stricter than the users can satisfy. Common culprits are a required field hidden on the edit screen, a condition against a project role nobody has been added to, or a post-function from a Marketplace app that silently expired. We trace the transition, the scheme and the user's roles to find which.
JSM is a solid choice for internal IT and dev-adjacent support, especially if the business already uses Jira. For customer-facing support where the audience is non-technical, Intercom, Zendesk or Help Scout usually fit better. We are happy to compare them against your actual case mix before recommending.
The quote is free. Tell us what the instance looks like and what is going wrong and we come back with a price before any work begins.
Free estimate
Tell us what the instance looks like and what is going wrong and we come back with a plan and a price.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: