Notes from the work

One email when a tutorial or migration write-up goes live. Nothing else, and an unsubscribe link in every email.

LeanZero

Two people in Romania doing Atlassian migrations, Forge apps and practical AI work for teams that would rather talk to the person doing the job. Most of what we learn ends up on this site.

Services

  • Atlassian migrations
  • Atlassian FastShift
  • Atlassian maintenance
  • Forge app development
  • AI development consultation

Topics

  • Jira
  • Jira Service Management
  • Confluence
  • Bitbucket
  • Atlassian Forge
  • Cloud Migration
  • Local AI
  • AI Coding
  • Certifications
  • Atlassian Team
  • All topics

Company

  • Blog
  • Tutorials
  • Contact

Community

  • Join Discord
  • Support this site

© 2026 LeanZero. All rights reserved.

Privacy policyTerms of service24/7 SupportTrust centerSecurityDPALegal notice
  1. Home
  2. Blog
Knowledge Base

Atlassian insights & tutorials

Real Atlassian solutions to real problems — no fluff, no SEO spam.

Read the latestFollow the tutorials
JiraConfiguration, workflows and fixes from real projectsLocal AIModels and agents running on your hardwareAI codingCoding tools and workflows tested in practice

Articles 2

All topicsAI CodingAtlassian ForgeAtlassian TeamBitbucketCertificationsCloud MigrationCogniRunnerConfluenceCost SlasherJiraJira Service ManagementLeanZero ManagementLocal AISentinel Vaultgoose Local Edition
Migrate Jira users and groups: the same-name group merge that escalates permissions
ArticleCloud Migration

Migrate Jira users and groups: the same-name group merge that escalates permissions

When you migrate Jira users and groups, a group whose name already exists on the Cloud site is linked to it by name. Its members inherit whatever that Cloud group can do. Here is how it works in JCMA and in Cloud-to-Cloud copy, and the audit to run first.

Mihai PerdumSep 24, 20265 min read

More articles

Atlassian Cloud Architecture: Organization, Site, Product, and What a Migration Crosses
ArticleCloud Migration

Atlassian Cloud Architecture: Organization, Site, Product, and What a Migration Crosses

An Atlassian Cloud tenant has a real shape: one organization, one or more sites under it, a product provisioned per site, and a directory that decides who gets in. This is that shape, sourced from Atlassian's own admin docs, plus the part that actually matters for a migration: a Data Center move crosses every one of those boundaries fresh, while a Cloud-to-Cloud move keeps identity and uses a documented tool with its own documented gaps.

Mihai PerdumSep 16, 202615 min read

Found my advice helpful?

If I helped you solve something for free, coffee money is always appreciated (but never expected).

Buy Me a Coffee

Join the community

Join the community to ask questions, share your work, and connect with other professionals.

Join Discord