Hello everyone, 👋
I’m currently preparing an Atlassian admin handover for my colleagues. One question keeps coming back: could someone use this when something has just stopped working?
For this Remix example, I used a small service desk handover with fictional details.
Before
The original page explains the responsibilities, daily checks, troubleshooting steps, configuration changes and weekly review. This screenshot shows an excerpt from the written handover.
After
I used Remix with Rovo to turn it into an infographic: Who owns the next step?
My first version was a simple summary. I refined the prompt to show the decision and its owner, with a clear YES/NO branch:
- Ticket intake stopped or several users affected → contact the Atlassian administrator immediately.
- Other issues → the admin queue, with an owner and a next step.
The final visual also brings together the roles, checks for missing emails and failed automation, and the approval steps before changing configuration.
I checked the escalation criteria and change checklist against the written source. In Confluence, I kept the full procedure linked and added a handover template for the current status, evidence, next action, owner and target date.
That makes the visual useful as a quick starting point, with the detail still available when a colleague needs it. And i literally love it :)
Arkadiusz Wroblewski
IT Application Specialist & Atlassian Platform Owner
Eckelmann AG
