Real Atlassian solutions to real problems — no fluff, no SEO spam.
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.
A blocks link in Jira records a relationship. On Free and Standard it reschedules nothing. Here's the engine we put behind it, the required-start rule that's easy to get subtly wrong, and what it still can't do.
A saved filter is a string, not a binding. I measured what cf[10042] actually resolves to on a destination site, and where Data Center to Cloud and Cloud to Cloud each fail silently.
A rule reads a dropdown answer off a Jira form, runs clean, logs no error, and leaves the field empty. Two things are wrong and both are in the rule rather than the log. Here is the mechanism, the full field-type mapping, and the check that decides whether any of it applies to you: there are two unrelated features called Forms and only one of them automation can see.
