We analyzed 8 examples of how Atlassian handles error states across their product, spanning 5 different approaches: inline validation, toast notification, modal dialog, in-context error, full-page error.
Atlassian — Jira / Work item detail
Jira work item detail view showing an access-denied state with a padlock illustration, indicating the user lacks permission to view the requested work item
Atlassian — Jira / 404 page
Jira 404 page showing a not-found state with an illustration of a person examining a map, indicating the requested page does not exist
Atlassian — Jira / Create Task modal
Jira Create Task modal with a toast notification at the bottom-left indicating the work item could not be created due to a server-side error
Atlassian — Teams / Team profile
Atlassian Teams profile page with a toast notification at the bottom-left indicating that a Slack integration could not be added to the team
Atlassian — File preview overlay
Confluence or Jira file preview overlay showing a file that could not be rendered, with a broken-document illustration and a download fallback
Atlassian — Assets / Dashboard / Add widget panel
Assets dashboard Add widget side panel showing an inline error below the Metric dropdown, indicating that options could not be loaded from the server
Atlassian — Jira / Create Task modal
Jira Create Task modal with inline field validation showing a required-field error on the Summary field, with a red border and error message below the input
Atlassian — Assets / Dashboard / Manage access modal
Assets dashboard Manage access modal showing an error state with a warning illustration, indicating that dashboard access settings could not be loaded