# How We Build Archives - Inside Atlassian

Research, expert perspectives, and product announcements from Atlassian on how teams can work smarter with AI. Subscribe for monthly insights on the future of teamwork.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Scaling Jira to ~6M Versions

DevFeed: [Scaling Jira to ~6M Versions](<https://devfeed.tech/articles/scaling-jira-to-6m-versions-129709.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/jira/scaling-jira-to-6m-versions>)

Author: Jovana Dunisijevic

Published: 2026-11-11T08:10:36Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [jira](<https://devfeed.tech/topics/jira.md>), [search-engines](<https://devfeed.tech/topics/search-engines.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Amazon OpenSearch Service](<https://devfeed.tech/topics/amazon-opensearch-service.md>)

Tags: [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [jira](<https://devfeed.tech/tags/jira.md>), [loading](<https://devfeed.tech/tags/loading.md>), [memory](<https://devfeed.tech/tags/memory.md>), [query](<https://devfeed.tech/tags/query.md>), [release](<https://devfeed.tech/tags/release.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [search](<https://devfeed.tech/tags/search.md>)

### AI overview

Jira Search cut P99 resolution time for project-scoped version queries from about 18 seconds to 92 milliseconds by detecting project clauses and limiting version lookups to that project. This reduced the scan from millions of rows to hundreds and estimated memory use from about 3 GB to 250 KB. For unscoped queries, Atlassian split large ID fetches into parallel chunks: scale tests reduced SQL fetch time from over 30 seconds to under 700 milliseconds. Batch size had to balance index use against too many parallel calls. An array-based PostgreSQL query was considered, but its performance was not established; the post says that requires direct testing with representative data and concurrency. The excerpt also describes plans to index version data in the OpenSearch-based JSIS search engine.

### Source excerpt

Jira Search has to keep up as our customers' data grows. Our largest customers tracks millions of releases, and for us that meant supporting nearly 6 million software release versions. At that scale, even preparing a search query became a bottleneck. It relied on loading versions into memory and filtering them there, which stopped being [...] The post Scaling Jira to ~6M Versions appeared first on Inside Atlassian.

## 3 lessons from rebuilding Atlassian's product development lifecycle for people and agents

DevFeed: [3 lessons from rebuilding Atlassian's product development lifecycle for people and agents](<https://devfeed.tech/articles/3-lessons-from-rebuilding-atlassian-s-product-development-lifecycle-for-people-and-agents-126752.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/how-we-build/3-lessons-from-rebuilding-atlassians-product-development-lifecycle-for-people-and-agents>)

Author: Lia Zneimer

Published: 2026-11-10T16:14:48Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [atlassian](<https://devfeed.tech/topics/atlassian.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [atlassian](<https://devfeed.tech/tags/atlassian.md>), [design](<https://devfeed.tech/tags/design.md>), [development](<https://devfeed.tech/tags/development.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [faster](<https://devfeed.tech/tags/faster.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [pdlc](<https://devfeed.tech/tags/pdlc.md>), [people](<https://devfeed.tech/tags/people.md>), [product](<https://devfeed.tech/tags/product.md>), [product-development](<https://devfeed.tech/tags/product-development.md>)

### AI overview

Atlassian's central finding is that faster AI execution does not by itself improve products; teams need to redesign how product, design, and engineering collaborate, especially across handoffs. Its three principles are to direct human attention to consequential decisions, carry shared context through the work, and widen contribution while preserving expert accountability. In security work, agents prepare fixes for 52% of vulnerabilities, saving roughly 50 engineering days a week, with engineers judging whether proposed fixes are safe to ship. In a Confluence pilot, shared specifications became Jira tasks for agents; two production features shipped in 2 and 4 developer weeks versus historical estimates of 30 and 40. An internal initiative enabled over 50 PMs and designers to ship more than 100 engineering-approved changes in three months, with engineers scoping and reviewing the code. Atlassian says to evolve tasks first, then skills, then roles. These examples come from the supplied excerpt.

### Source excerpt

AI makes execution faster. Improving the entire PDLC requires evolving the way teams work together. The post 3 lessons from rebuilding Atlassian's product development lifecycle for people and agents appeared first on Inside Atlassian.

## The Atlassian AI PDLC Playbook

DevFeed: [The Atlassian AI PDLC Playbook](<https://devfeed.tech/articles/the-atlassian-ai-pdlc-playbook-126751.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/guides-research/ai-product-development-lifecycle-playbook>)

Author: Lia Zneimer

Published: 2026-11-10T15:40:49Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [atlassian](<https://devfeed.tech/topics/atlassian.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [lead time](<https://devfeed.tech/topics/lead-time.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-productivity](<https://devfeed.tech/tags/ai-productivity.md>), [atlassian](<https://devfeed.tech/tags/atlassian.md>), [context](<https://devfeed.tech/tags/context.md>), [customer-value](<https://devfeed.tech/tags/customer-value.md>), [days](<https://devfeed.tech/tags/days.md>), [design](<https://devfeed.tech/tags/design.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [experiments](<https://devfeed.tech/tags/experiments.md>), [faster](<https://devfeed.tech/tags/faster.md>), [guide](<https://devfeed.tech/tags/guide.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [pdlc](<https://devfeed.tech/tags/pdlc.md>), [pilot](<https://devfeed.tech/tags/pilot.md>), [product-design](<https://devfeed.tech/tags/product-design.md>), [product-development](<https://devfeed.tech/tags/product-development.md>), [production](<https://devfeed.tech/tags/production.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [prototypes](<https://devfeed.tech/tags/prototypes.md>)

### AI overview

Atlassian's takeaway is that AI productivity gains require redesigning the product development lifecycle, not just speeding up individual tasks. Its approach has agents handle repeatable work while people make consequential decisions, carries context across work, and broadens contribution while experts remain accountable for quality. In reported examples, agents investigate vulnerabilities and propose fixes, saving about 50 engineering days weekly, with engineers approving each change before merge. An internal pilot estimated that designers' production-shaped prototypes could make design-to-build about 50% faster. An AI orchestrator coordinating build, test, and analysis agents reduced idea-to-first-build time from 30 days to 3, with people making critical calls. Atlassian says it is testing these methods across greenfield and legacy projects, including systems with strict security requirements.

### Source excerpt

Rethinking how products get built AI has accelerated individual work, but that doesn't automatically make teams better at building products. See how Atlassian is redesigning its product development lifecycle (PDLC) to connect people, agents, and context. By the numbers Transforming our own teams Building better products won't come from AI alone. We need to rethink [...] The post The Atlassian AI PDLC Playbook appeared first on Inside Atlassian.

## Teaching a 4B Model to Think Like a Policy Expert

DevFeed: [Teaching a 4B Model to Think Like a Policy Expert](<https://devfeed.tech/articles/teaching-a-4b-model-to-think-like-a-policy-expert-117705.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/how-we-build/teaching-a-4b-model-to-think-like-a-policy-expert>)

Author: dkoudsi@atlassian.com

Published: 2026-11-04T16:55:00Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [Fine-tuning](<https://devfeed.tech/topics/fine-tuning.md>), [post-training](<https://devfeed.tech/topics/post-training.md>), [dpo](<https://devfeed.tech/topics/dpo.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [Prompt Engineering](<https://devfeed.tech/topics/prompt-engineering.md>), [Inference](<https://devfeed.tech/topics/inference.md>)

Tags: [acceptable-use](<https://devfeed.tech/tags/acceptable-use.md>), [adversarial](<https://devfeed.tech/tags/adversarial.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [atlassian](<https://devfeed.tech/tags/atlassian.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [content-moderation](<https://devfeed.tech/tags/content-moderation.md>), [data](<https://devfeed.tech/tags/data.md>), [direct-preference-optimization](<https://devfeed.tech/tags/direct-preference-optimization.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [latency](<https://devfeed.tech/tags/latency.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [rovo](<https://devfeed.tech/tags/rovo.md>), [search](<https://devfeed.tech/tags/search.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

Atlassian fine-tuned NVIDIA Nemotron 3 Nano 4B as a fast first-pass filter for Acceptable Use Policy violations, routing suspicious cases to a larger 20B model. Prompt engineering on the 20B model had plateaued at 50.9% recall, and its inference-time reasoning added latency. The team trained the 4B model with supervised examples containing labels and reasoning traces, then used Direct Preference Optimization to refine difficult cases. Synthetic training data included benign, violating, and adversarial examples; evaluation used balanced and adversarial sets. The article reports that the fine-tuned model reached 87.0% precision and 75.5% recall, while the overall moderation system became 53% faster and supported 42% more throughput. AI agents helped run over 300 experiments. The reported results are Atlassian's internal evaluation and production claims.

### Source excerpt

Content moderation at Atlassian's scale means making millions of real-time decisions every message, prompt, and query that flows through Rovo Chat, Rovo Search, and more has to be checked before a response is served. That puts moderation squarely on the critical path of every user request. Latency isn't a nice-to-have. It's a product requirement. For [...] The post Teaching a 4B Model to Think Like a Policy Expert appeared first on Inside Atlassian.

## How enterprise addmins are taking control of cloud performance.....and why it matters

DevFeed: [How enterprise addmins are taking control of cloud performance.....and why it matters](<https://devfeed.tech/articles/how-enterprise-addmins-are-taking-control-of-cloud-performance-and-why-it-matters-109446.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/how-we-build/enterprise-admins-cloud-health>)

Author: amacaraeg@atlassian.com

Published: 2026-10-30T20:17:54Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>), [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [atlassian](<https://devfeed.tech/topics/atlassian.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [administration](<https://devfeed.tech/tags/administration.md>), [atlassian](<https://devfeed.tech/tags/atlassian.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automated-remediation](<https://devfeed.tech/tags/automated-remediation.md>), [availability](<https://devfeed.tech/tags/availability.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [beta](<https://devfeed.tech/tags/beta.md>), [bitbucket](<https://devfeed.tech/tags/bitbucket.md>), [business-context](<https://devfeed.tech/tags/business-context.md>), [business-processes](<https://devfeed.tech/tags/business-processes.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [control](<https://devfeed.tech/tags/control.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [it](<https://devfeed.tech/tags/it.md>), [migration](<https://devfeed.tech/tags/migration.md>), [performance](<https://devfeed.tech/tags/performance.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

Atlassian's System Health gives cloud admins visibility into site health and tools to address performance issues, while Atlassian manages underlying infrastructure and customers manage configuration and usage factors. Incident Insights provides site-specific alerts across core apps and is available to all Atlassian Cloud customers. Performance Insights, in open beta for Cloud Enterprise, shows end-user load times and factors such as data volume, configuration complexity, and client setup, then links findings to cleanup recommendations and self-service tools; Jira also has Rovo-powered diagnostics. The article says admins can use these insights to investigate issues without waiting for support, and Data Center migrants can establish a performance baseline. Atlassian also publishes Jira Cloud data limits, Fast/Moderate/Slow bands based on TTVC, and client setup guidelines including HTTP/3, speeds above 10 Mbps, and 8+ CPU cores.

### Source excerpt

Moving to cloud doesn't mean giving up visibility. Here's how enterprise admins are taking site performance into their own hands. Whether you're a long-standing Atlassian Cloud customer scaling to tens of thousands of users, expanding into new products, or completing a migration from Data Center to Cloud, one question comes up consistently: how do I [...] The post How enterprise addmins are taking control of cloud performance.....and why it matters appeared first on Inside Atlassian.

## Jira's depth, on demand: designing an MCP server around jobs, not endpoints

DevFeed: [Jira's depth, on demand: designing an MCP server around jobs, not endpoints](<https://devfeed.tech/articles/jira-s-depth-on-demand-designing-an-mcp-server-around-jobs-not-endpoints-105639.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/how-we-build/jira-depth-on-demand>)

Author: Jovana Dunisijevic

Published: 2026-10-28T21:52:28Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [jira](<https://devfeed.tech/topics/jira.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [software-development](<https://devfeed.tech/topics/software-development.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [jira](<https://devfeed.tech/tags/jira.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [server](<https://devfeed.tech/tags/server.md>)

### AI overview

Atlassian's Jira MCP v2 groups tools around user jobs so the server coordinates multiple Jira API calls while the agent focuses on outcomes. Its 52 tools cover more than 100 APIs; six are always available and 46 are deferred through discovery and risk-tiered execution. The design uses intent-based tools, action enums, name-based lookups, actionable errors, and JQL and detail-level options. Workflow checks still apply: closing an issue may require first listing valid transitions and required fields. OAuth 2.1 preserves the signed-in user's permissions, while admins can separately scope destructive and administrative tools; Atlassian Guard policies can restrict MCP access to projects or sensitive content. In an internal 84-case October evaluation, v2 passed 57 of 62 tasks both versions could attempt, versus 54 for v1, and reduced failed calls from 0.20 to 0.09 per run. v2 also completed 17 cases unsupported by v1. Internal benchmarks report up to 25% fewer tokens for the same Jira work; a separate comparison found loading the full catalog used roughly 2.2 times the cumulative input tokens of deferred loading. Some evaluation cases still fail, including one where the returned backlog,

### Source excerpt

In this blog we're going to walk you through our Jira MCP tool design journey, a critical part of Atlassian's MCP AI capability, supporting more than 15M calls every weekday. "MCP on Jira is the greatest advance since the airplane." - real quote from a happy Jira MCP customer Ask an agent to close a [...] The post Jira's depth, on demand: designing an MCP server around jobs, not endpoints appeared first on Inside Atlassian.

## Meet the Forward Deployed Engineer

DevFeed: [Meet the Forward Deployed Engineer](<https://devfeed.tech/articles/meet-the-forward-deployed-engineer-81958.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/how-we-build/meet-the-forward-deployed-engineer>)

Author: lzneimer

Published: 2026-10-07T07:30:00Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [developer-relations](<https://devfeed.tech/topics/developer-relations.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai-engineer](<https://devfeed.tech/tags/ai-engineer.md>), [ai-transformation](<https://devfeed.tech/tags/ai-transformation.md>), [customer](<https://devfeed.tech/tags/customer.md>), [develop](<https://devfeed.tech/tags/develop.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [fde](<https://devfeed.tech/tags/fde.md>), [fde-program](<https://devfeed.tech/tags/fde-program.md>), [forward-deployed-engineer](<https://devfeed.tech/tags/forward-deployed-engineer.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>)

### AI overview

Atlassian describes its Forward Deployed Engineer program, which embeds AI engineers with enterprise customers to build solutions for specific business goals and feed lessons back into product teams. The post says the team has grown to 46, with plans to reach 100, and outlines customer examples and the program's discovery and implementation process.

### Source excerpt

What are FDEs, and why is Atlassian investing in them? The post Meet the Forward Deployed Engineer appeared first on Inside Atlassian.

## Atlassian's Forward Deployed Engineering Playbook

DevFeed: [Atlassian's Forward Deployed Engineering Playbook](<https://devfeed.tech/articles/atlassian-s-forward-deployed-engineering-playbook-81954.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/guides-research/forward-deployed-engineering-playbook>)

Author: lzneimer

Published: 2026-10-04T22:44:35Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [AI Engineering](<https://devfeed.tech/topics/ai-engineering.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>)

Tags: [ai-engineering](<https://devfeed.tech/tags/ai-engineering.md>), [applied-ai](<https://devfeed.tech/tags/applied-ai.md>), [auditability](<https://devfeed.tech/tags/auditability.md>), [compute](<https://devfeed.tech/tags/compute.md>), [forward-deployed-engineering](<https://devfeed.tech/tags/forward-deployed-engineering.md>), [governance](<https://devfeed.tech/tags/governance.md>), [guide](<https://devfeed.tech/tags/guide.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [scale](<https://devfeed.tech/tags/scale.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Atlassian's Forward Deployed Engineering playbook describes how senior engineers work with enterprise teams to identify measurable AI use cases, build production agents and integrations, and redesign workflows. Its lessons emphasize selecting consequential problems, incorporating permissions and security into architecture, embedding AI in existing workflows, and optimizing system economics. It also presents company examples with reported savings and efficiency outcomes.

### Source excerpt

Why enterprise AI stalls Across our Forward Deployed Engineering (FDE) engagements, the same four reasons enterprise AI stalls show up again and again. This Playbook outlines what we've learned from solving them in the field. By the numbers How it works Atlassian FDEs are senior engineers, bringing AI engineering and applied AI together in a [...] The post Atlassian's Forward Deployed Engineering Playbook appeared first on Inside Atlassian.

## From fake interviews to malicious repositories: Disrupting Contagious Interview

DevFeed: [From fake interviews to malicious repositories: Disrupting Contagious Interview](<https://devfeed.tech/articles/from-fake-interviews-to-malicious-repositories-disrupting-contagious-interview-81955.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/how-we-build/disrupting-contagious-interview>)

Author: dkoudsi@atlassian.com

Published: 2026-09-21T21:01:29Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [Threat Research](<https://devfeed.tech/topics/threat-research.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>)

Tags: [api-keys](<https://devfeed.tech/tags/api-keys.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [github](<https://devfeed.tech/tags/github.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [repositories](<https://devfeed.tech/tags/repositories.md>)

### AI overview

The post describes Atlassian's analysis and disruption of Contagious Interview, a campaign that hides malware in coding assessment repositories used in fraudulent recruitment. The payloads can steal credentials and access corporate systems. It outlines recurring campaign patterns, platform response, and precautions for individuals and organizations, including isolating assessment environments and monitoring for suspicious activity.

### Source excerpt

Software developers and IT professionals are increasingly being targeted through fraudulent recruitment processes that exploit their trust in established development platforms. Candidates are invited to complete seemingly legitimate coding assessments hosted in publicly accessible repositories on services such as Bitbucket, GitHub, and GitLab. The repositories appear to be fully developed applications, with thousands of lines [...] The post From fake interviews to malicious repositories: Disrupting Contagious Interview appeared first on Inside Atlassian.

## How Atlassian built a scalable synthetic data engine

DevFeed: [How Atlassian built a scalable synthetic data engine](<https://devfeed.tech/articles/how-atlassian-built-a-scalable-synthetic-data-engine-81956.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/how-we-build/how-atlassian-built-scalable-synthetic-data-engine>)

Author: Jovana Dunisijevic

Published: 2026-09-21T04:35:03Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [scalable-architecture](<https://devfeed.tech/topics/scalable-architecture.md>), [sharding](<https://devfeed.tech/topics/sharding.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>)

Tags: [atlassian](<https://devfeed.tech/tags/atlassian.md>), [data](<https://devfeed.tech/tags/data.md>), [engine](<https://devfeed.tech/tags/engine.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [synthetic-data](<https://devfeed.tech/tags/synthetic-data.md>)

### AI overview

Atlassian describes Data Brewery, a configuration-driven platform for generating large synthetic Jira and Confluence datasets for migration testing. It generates table rows independently, then injects foreign keys in batches to preserve relational integrity while improving parallelism, memory use, and retry handling. The article also discusses schema drift and conditional field rules that remain under development.

### Source excerpt

Term Meaning Product An application whose data we generate eg. Jira, Confluence etc. Entity Product level business object/data type (eg. user, space, work item, comment, page). Space Jira container for work (formerly Jira project) Work Item Jira ticket(a bug, story, epic or task). Work items live in a space Attachment A file on a Jira work [...] The post How Atlassian built a scalable synthetic data engine appeared first on Inside Atlassian.

## Meet Teamoji: Atlassian's Custom Emoji System Built for the Future of Work

DevFeed: [Meet Teamoji: Atlassian's Custom Emoji System Built for the Future of Work](<https://devfeed.tech/articles/meet-teamoji-atlassian-s-custom-emoji-system-built-for-the-future-of-work-81957.md>)

Original publisher: [Read original article](<https://www.atlassian.com/blog/how-we-build/meet-teamoji-atlassians-custom-emoji-system-built-for-the-future-of-work>)

Author: Aaron Booth

Published: 2026-09-16T22:29:49Z

Content type: article

Language: en

Sources: [How We Build Archives - Inside Atlassian](<https://devfeed.tech/sources/how-we-build-archives-inside-atlassian.md>)

Topics: [Vercel prism](<https://devfeed.tech/topics/vercel-prism.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [Emoji](<https://devfeed.tech/topics/emoji.md>), [atlassian](<https://devfeed.tech/topics/atlassian.md>)

Tags: [brand](<https://devfeed.tech/tags/brand.md>), [delight](<https://devfeed.tech/tags/delight.md>), [design](<https://devfeed.tech/tags/design.md>), [emoji](<https://devfeed.tech/tags/emoji.md>), [future-of-work](<https://devfeed.tech/tags/future-of-work.md>), [how-we-build](<https://devfeed.tech/tags/how-we-build.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

Atlassian describes its custom Teamojis, a brand emoji set for product and customer-facing use. The design combines saturated colors and humanistic shapes with expressive personality and a professional tone for enterprise customers.

### Source excerpt

Meet Teamoji -- Atlassian's custom brand emoji set built for product and customer-facing surfaces. Designed with a vibrant, humanistic system that balances expressive delight with enterprise trust. Small in size, big in personality The post Meet Teamoji: Atlassian's Custom Emoji System Built for the Future of Work appeared first on Inside Atlassian.