Abaho Katabarwa (Katabarwa Labs) Atlassian Partner

Hi @Likhita Biyyala, good question, and the two-org detail matters. From Atlassian's link fixing docs, check these before the production run: * Timing. Links can only be updated for 2 weeks after a migration. After that, the migration data used to match old and new links is deleted, so run link fixing right after each…

Hi @Likhita Biyyala, to confirm Tobi's suggestion: link fixing does cover cloud-to-cloud migrations, and it's the supported way to deal with this. After a cloud-to-cloud migration, URLs that point at the old site (pasted links and Smart Links included) keep pointing at the old site, because the content now lives under a…

Hi @Likhita Biyyala, to add to Ashish's answer, the development panel can usually be brought back after the migration rather than lost for good. The commits, branches and pull requests live in Bitbucket and are matched to Jira by the work item keys in commit messages and branch names. Once the target site is connected to…

Hi @Frohnapfel, Simon, this is a known limitation rather than something misconfigured on your side. Outlook groups messages into a conversation using its own headers (Thread-Topic and Thread-Index) together with the subject. The customer's original email is sent by Outlook with those headers, but the notifications Jira…

One thing worth adding to Tobi's point about native Approvals, because it matters for your case specifically: approvals work on pages, not on live docs. Since your controlled document is a live doc, converting it is the prerequisite step, not an optional tidy-up. It is on the document itself, under ... (More actions) >…

Arkadiusz has the right ticket: JSDCLOUD-18992 is the one to watch, and it is still Gathering Interest with no fix date. One workaround worth the effort if you need the full list programmatically today. The desk-customer endpoint under-reports, but organization membership is exposed through a different endpoint that…

JSM's built-in outgoing notification system only logs failures, which is why there is no way in the native UI to confirm CSAT sends short of the Automation mirror approach above. The comment referencing JSDCLOUD-16298 is accurate: a native send audit does not exist yet. Full disclosure: I work for Katabarwa Labs and we…

Tomislav's answer is the honest one. At 800+ projects almost everyone lands on scripts plus a manual pass. The part that made it painful for me was a gap the script itself creates: it can tell you a user has Browse on a project, but not why. Was it one of their twelve group memberships? A project role? A permission scheme…

@Oliver Wright@Staffan Redelius's advice above is solid: start with groups, minimize custom permission schemes, and lean on an identity provider like Entra ID for licensing. Those are the right structural choices as you scale. One thing that gets harder as projects multiply is simply knowing the current state of who can do…

The accepted answer about scoping the JQL is the right structural fix. The step before it is seeing your current blast radius: who holds Manage Sprints today, via which group or role, and across which projects. That is the audit step our app Access Governance Reporter is built for: a per-user breakdown of every project and…

[@mention Audra Bonacki here] The answers above cover what the limit is: at most 50 grantees (users, groups, and roles combined) on any single permission inside a permission scheme. The part nobody has touched is the practical one: when the optimize button hangs, you are left doing the reduction by hand, and the risk is…

@Mike Perera On your last question: there is no manual sync you can trigger from the Atlassian side, and support generally cannot force one either. The sync is driven by your identity provider pushing through SCIM, so the fix happens in the provisioning logs the folks above pointed to. For three stuck users out of a full…

Hey @Mark van Beek , The community answer pointing you to Space Settings > Restricted Pages is exactly right for the immediate fix. Page restrictions in Confluence override space permissions entirely, which is why being a space admin was not enough to see the content. Stripping the view restrictions from those pages should…