Support
Relevo is supported by email, Monday to Friday. We aim to answer within two business days. Write to juanp.orjuelar@gmail.com and include your Jira site address, what you expected, and what happened instead. Please do not send work item content or screenshots that show confidential data.
Getting started
- In Jira, open Apps → Relevo.
- Choose who is going away and the first and last day, then press Build handover.
- Review the suggested covers, write a note on each item that cannot wait, and press Send handover.
- On your first day back, open the handover to read what changed and take your work back.
Some context sources show as unavailable
Teams, pull requests, goals and projects come from the Teamwork Graph. An organisation admin has to grant those scopes: in Atlassian Administration, open Apps → Sites → your site → Connected apps → Relevo → Permissions. Relevo works without them, using Jira history alone.
An item says "Not handed over"
Jira refused the change, most often because you lack the "Assign issues" permission in that project, or the cover cannot be assigned work there. The message next to the item is the one Jira returned.
A work item I expected is missing from the plan
Relevo shows open work items assigned to the person that you are allowed to see, up to 100 per handover. Finished items and items in projects you cannot browse are left out.
The Relevo agent does not appear in Rovo
Rovo has to be enabled for your site. Agents that come with apps are listed in Rovo's agent browser after the app is installed.
Connecting your own AI client
An admin enables the tools under Connected apps → Relevo, then the client connects to the app's endpoint on the Atlassian MCP server. The tools are read-only.
Security reports
If you believe you have found a vulnerability, write to the same address with the subject "Security". We acknowledge within two business days.