Running Jira?

Jira workflows or migration stuck? We sort it out.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

jira-automation.log

still broken

What it is

Jira at a glance

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.

Type
Project and issue tracker
First released
2002
License
Proprietary SaaS, per-user pricing
Maintained by
Atlassian
Typically used for
Software project tracking, agile sprints, service management, incident response, business workflow tracking

The honest version

Jira pros and cons

No technology is all upside. This is where Jira earns its place and where it tends to cause trouble.

Where Jira is strong

  • Deep agile supportScrum and Kanban boards, backlogs, sprints, versions and velocity reports are first-class rather than bolted-on plugins, which matters for teams that measure themselves on them.
  • Flexible workflows and schemesStatuses, transitions, validators, conditions and post-functions give real control over how issues move, which is the feature that keeps enterprise buyers coming back.
  • Powerful JQLThe query language is expressive, fast enough on cloud for most needs, and powers dashboards, filters, boards and automation rules without a separate reporting tool.
  • Automation for Jira is genuinely usefulRules for triggering transitions, posting comments, syncing fields and integrating with Slack or GitHub cover most of what teams used to build scripts for.
  • Marketplace apps fill the gapsScriptRunner, Tempo, Structure, Advanced Roadmaps and hundreds of others cover scheduling, time tracking, hierarchy and reporting needs beyond the base product.

Where Jira bites

  • Inherited instances get ByzantineYears of custom fields, workflow schemes, permission schemes and automation rules accumulate, and nobody fully owns the cleanup. Projects behave in ways nobody can explain.
  • Cloud and Server differ in important waysMarketplace apps, scripting, permissions and API behavior all differ between Cloud, Server and Data Center. A migration is rarely a straight copy.
  • Performance degrades with scaleLarge boards, broad JQL filters on huge projects, and dashboards with heavy gadgets all slow down past a few hundred thousand issues, especially on Cloud.
  • Automation rules are easy to loopA rule that edits an issue to a state that triggers the same rule is a classic foot-gun, and a loop can eat your monthly automation quota in minutes.
  • Pricing is per-user and climbs fastStandard, Premium and Enterprise tiers, plus the per-user cost of every Marketplace app, means a growing team sees a bill that climbs faster than headcount.
  • Permission model is unforgivingPermission schemes, project roles, group memberships and issue-level security interact in ways where one wrong edit can hide a whole project from the people who need it.

Sound familiar?

Common Jira problems we fix

The Jira problems that bring people to us, and what you have once each one is fixed.

Server end of life 2024

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

Automation rule 2,041 executions

An automation rule is looping

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

JQL could not be parsed

JQL queries will not load

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

FieldRequiredValidator failed

Workflow transitions reject the user

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

customfield_10234 missing

Custom fields are out of control

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

CSV import unknown user

CSV or JSM import fails on users

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

permission scheme missing Browse Projects

Users cannot see a project they should

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

Confluence link AccessDenied

Jira and Confluence drift apart

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

Jira help, from migration to cleanup

Call us for one bad workflow, or hand us the entire Jira instance.

Rescue
Workflows jammed, automation rules looping, or a migration stalled halfway. We get the instance working again and then explain what led to it.
Server to Cloud migration
Pre-migration audit, Marketplace app mapping, user and group reconciliation, and a tested cutover plan with a rollback window.
Workflow simplification
Inherited workflows walked through transition by transition, with the ones that nobody uses retired and the ones that matter documented.
Automation and ScriptRunner
Automation rules reviewed for loops and quota pressure, and ScriptRunner scripts audited, tested and brought into source control.
Permissions and governance
Permission schemes, project roles, issue security and application access reviewed so a user sees exactly what they should, nothing more and nothing less.
Managed Tech
Ongoing coverage: automation quota monitoring, Marketplace app updates, cloud migration follow-ups and a human responder when a permissions change goes sideways.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Jira alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Jira questions

Something else? Call+1 737 727 7327

Can you migrate us from Jira Server to Jira Cloud?

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.

Why is our Jira automation rule firing thousands of times?

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.

How do we clean up hundreds of custom fields?

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.

Our workflow transitions reject everyone, what happened?

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.

Should we use Jira Service Management for our help desk?

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.

How much does Jira help cost?

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

Jira giving you trouble?

Tell us what the instance looks like and what is going wrong and we come back with a plan and a price.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.