Hi Atlassian Community,
I’ve been experimenting with Rovo for a practical delivery management use case and wanted to share the experience to see if others have explored something similar.
As a Delivery Manager, one recurring challenge is understanding whether sprint capacity aligns with actual effort spent — especially when accounting for planned leave and expected utilisation.
I tested a Rovo workflow to compare:
• Planned sprint capacity (3-week sprint, adjusted for leave)
• Time logged in Jira tickets
• Expected utilisation threshold (e.g., 80% logged effort)
What impressed me was that Rovo could actually reason through the logic and generate a utilisation analysis in Confluence — which felt like a strong step toward smarter delivery insights.
However, I hit a few practical limitations:
• Processing can take 15–30 minutes for capacity vs logged effort analysis
• Re-prompting often triggers re-validation from scratch
• Jira time logs currently need to be manually exported to CSV and uploaded
This made me think about a potential opportunity for Rovo Agents.
Could a custom Rovo Agent connected directly to Jira time-tracking automate utilisation reporting and continuously generate sprint/weekly insights without manual intervention?
I’m curious:
Has anyone attempted a similar Rovo use case?
Is there a better way to approach this using existing Atlassian capabilities?
Could this be something better solved through automation rather than prompting?
Would genuinely love to learn from how others are approaching this.
Kind regards,
Febin
Contact: https://www.linkedin.com/in/febin-philipose/
