Real Atlassian solutions to real problems — no fluff, no SEO spam.
I passed the Claude Certified Architect and ACP-120 within days of each other. One of them changed how I build agentic workflows, and not for the reason I expected. Here is the honest version, and what I am building next.
A plan is built for one source-destination pair. Re-run it against another and cached IDs from tenant A land in tenant B. There is a fingerprint to stop that — and it declines to stop the plan most likely to be wrong.
A buffer task that absorbs slip until it can't, a plan that defends itself against edits made in Jira, and a write path that refuses rather than lies. Traced line by line, and set against what BigPicture and Structure.Gantt actually document.
Six reports were announced for retirement. Three were saved, three were not, and both dates in circulation have now passed in silence. Three different answers are going around and none of them come from Atlassian — here is where each one actually starts.
DC to Cloud spends its budget resolving who everyone is, because usernames do not exist in Cloud. Cloud to Cloud gives you identity for free and a first-party copy tool — then bills you for the specific things that tool does not take.
A widely accepted community answer says sub-tasks cannot skip a hierarchy level. Atlassian's own knowledge base says the opposite. I ran it on both project types: company-managed accepts it through the REST API and through the UI, team-managed refuses it in both, and half your reports cannot see the result.
For a year our workflow conditions evaluated a constant and gated nothing. 3.1.0 replaces that constant with ten checks that Jira runs itself. Here is what shipped, what I measured against a live Jira, and how it compares to what else is on the Marketplace.
Jira Cloud answers 303, Confluence answers 302, and an SSO-fronted Data Center answers with a login page. I measured the two Cloud cases end to end, and the failure that follows passes every audit you are likely to write.
A customer changes email domain and starts appearing twice in the reporter picker. Removing them from the project provably cannot fix it, the query that finds their tickets stays silent when it fails, and the reassign that clears them reports the wrong reason for refusing.
