QR codes for a public Atlassian Statuspage
Key Takeaway
Link a standing sign to your public status page. Use incident links for temporary notices and check the page from a customer’s perspective.
Point a standing service sign to your public status homepage. Use a specific public incident link for a temporary notice about that issue. Test the destination outside your admin session before putting either QR in front of customers.
Choose a destination that will outlast the notice
Use the status homepage for a sign people may keep seeing after the current incident is resolved. If a temporary notice names one active issue, the relevant incident can be the shortest route to its updates. Remove that notice when the issue no longer applies.
Atlassian’s Statuspage product guide distinguishes public and private pages. Its incident guide shows the public-facing incident and the separate management interface. Copy the customer-facing address from the page visitors actually see.
Match the QR to the life of the notice
| Placement | Destination | Review point |
|---|---|---|
| Standing lobby or support sign | Public status homepage | After a hostname or audience change. |
| Temporary notice naming a disruption | Public incident page for that issue | When the incident resolves or the notice is no longer accurate. |
| Restricted staff instruction | Approved internal status destination | Confirm the intended sign-in path before internal distribution. |
Worked example: a lobby sign during a booking outage
Imagine a venue with a permanent Check service status sign alongside its reception desk. That code points to the public status homepage. A temporary sign about a booking disruption points directly to the public incident.
After the incident is resolved, the venue removes the temporary sign. The permanent code still takes visitors to the current service status without a new print run.
Give people an option if they cannot scan
- Put a short, readable status address or your approved support route on the sign. Check it separately from the QR.
- Open the exact customer-facing address without your admin access and check the service name and audience.
- Review the wording after the incident changes. Replacing a QR destination does not change text that is already printed.
If you are placing the QR on a screen, use the digital signage guide to test the actual display.
How to create a Statuspage QR code in QRLynx
Verify the destination from the reader’s point of view.
Decide how long the notice will stay up
Use the status homepage for an ongoing sign. Pick the public incident page only for a notice tied to that incident.
Check the customer-facing address
Open the address outside the management session and verify the intended service and incident.
Enter the address in QRLynx
Choose Website / Link and paste the verified address into Website URL.
Choose whether the redirect may change
Use static for a stable address. A saved dynamic URL QR is useful when an authorized maintainer might move the destination later.
Download and add a fallback
Save a dynamic QR before printing. Use Download, give the artwork a clear service status label, and include a readable address or support route.
Test the finished notice
Scan it where it will be seen. Verify that the service name and wording match, then try the fallback without scanning.
Service status
Create a QR for your public status page
Use the customer-facing address you verified outside the admin session.
Frequently asked questions
Should a permanent sign link to the status homepage or a single incident?
Use the public status homepage if the sign will stay in place across several incidents. A link tied to one issue fits a temporary notice about that issue.
Which URL should I copy for a temporary incident notice?
Open the public-facing incident whose title matches the notice. Copy its address and verify that the intended reader can open it outside your management session.
Can a public sign link to a private status page?
A code can point to a private page, but it does not grant access. Use a customer-facing public status destination for a public sign and keep restricted destinations in approved staff material.
Should the QR take readers straight to the admin screen?
No. Use the address your audience is expected to open. Incident administration belongs in the management interface.
Do I need to change the QR for each incident update?
No, if updates appear at the address already printed in the QR. Replace the notice when the issue or wording no longer matches what people see.
Does scanning a status page QR subscribe a customer to alerts?
No. Opening the status page and subscribing to notifications are separate actions. Available subscription options depend on the page’s configuration.
What should the printed fallback say?
Print a readable status address or an approved support route and say what someone will find there. Test that route on its own.
What if we move the public status page to another URL?
Update a saved dynamic QR to the new verified address if you have authority to do so. Static artwork still contains the old address. Update any printed fallback that changed.
Does a scan count prove a customer saw or received an update?
No. A scan indicates someone interacted with the QR. It does not establish that a customer read an incident update or received a notification.
