Skip to content

SYSTEM Cited by 3 sources

Jira

Jira is Atlassian's issue-tracking and project-management product. Issues live under Projects (also called spaces in the newer product taxonomy), can be grouped into Epics, and carry labels for cross-cutting tagging. Jira's workflows define the state machine (Open → In Progress → Done, with customisable transitions). The cloud-hosted multi-tenant deployment is Jira Cloud.

Role on this wiki

Jira appears on the wiki at three altitudes:

  • As a downstream sink for automated tickets — the canonical alert- channel-to-Jira auto-ticket workflow: an automated signal (accessibility violation, monitoring alert, security scan) is routed through a Slack workflow that creates a pre-populated Jira ticket with a canonical label and placement, collapsing the alert-to-triage step into a single button click.
  • As a multi-tenant SaaS exhibiting configuration-bloat failure modes at scale — Jira Cloud as the host platform whose limits and guardrails plus optimisation tools make it the canonical wiki instance of the configuration-bloat problem and the optimisation- tools answer architecture.
  • As a workflow-substrate for AI agents — the canonical wiki instance of the work-item-as-agent-prompt framing. Jira's structured custom fields encode the agent's task brief; Jira's workflow state machine carries the human approval gate; Jira's workflow transition automations carry per-procedure custom system prompts that trigger the agent. Atlassian's first-party Add an agent to workflow transitions feature is the integration surface; Atlassian's own Jira team used it for KTLO automation (stale-flag cleanup, flaky-test remediation) producing 500+ merged PRs in 70 days on the Jira repo.

Jira Cloud limits and guardrails (per space)

As Jira scales to "100k+ users and beyond", Atlassian introduced hard caps on configuration entities to protect core experiences (view, search). Per Atlassian's data limits and guardrails, the published caps include:

  • Up to 700 custom fields per space.
  • Up to 150 work types (formerly issue types) per space.
  • Up to 20,000 field options per field.
  • Up to 50 issue security levels per space.
  • Up to 50 grants per permission.
  • Plus "limits around versions, workflows, components and priorities."

(Source: sources/2026-05-14-atlassian-optimisation-tools-for-jira-reducing-configuration-bloat)

Optimisation tools architecture

Hard limits create a corollary problem: how do tenants already over the cap get back under without breaking their setups? Atlassian's answer is the Jira Optimisation Tools — admin experiences plus async backend workflows that:

  • Report unused / low-value configuration entities per space, computed asynchronously by the Pre-computation Framework.
  • Remediate via opinionated bulk actions consuming those reports (dissociate unused fields, split field configuration schemes, clean up unused work types).
  • Surface all of this through the Site Optimiser admin dashboard.

The reporting + remediation contract is detailed in systems/atlassian-jira-optimisation-tools and the underlying batch-orchestration platform in systems/atlassian-precomputation-framework.

Seen in

Last updated · 542 distilled / 1,571 read