Rovo dev demo for mBank Team

[Jarek Olchowik]

Hi Atlassian Community,

I'm Jarosław Olchowik, IT Manager leading AI Adoption at mBank (top-4 bank in Poland/CEE, ~5.7M clients, strong in-house engineering).

We’re currently evaluating agentic AI solutions for a use case like:
Jira ticket → autonomous code fix → PR in Bitbucket for human review

Rovo Dev looks very promising in this space, and I’d love to:

• see a live demo, and
• get in touch with the right Atlassian team to explore a potential POC (4–6 weeks).

Key aspects for us (regulated EU bank):

• Jira + Bitbucket (DC/Cloud) integration
• EU data residency
• deployment model (cloud / VPC / hybrid)
• SSO / SAML
• audit logs
• end-to-end “ticket → PR” flow

If anyone from Atlassian (or community members) can:

• point me to the right contact, or
• help arrange a demo / intro call

I’d really appreciate it 🙌

Happy to share a short briefing pack to provide more context.

Thanks in advance!
Jaroslaw

[Samuil Enchev]

Hi @Jarek Olchowik

Great to meet you! It’s exciting to see mBank exploring agentic AI for the "Ticket → PR" flow—Rovo Dev is built exactly for this use case.

I have just emailed you the direct contact details for the Account Owner for mBank.pl. I’ve briefed them on your request, and they are expecting your email to coordinate the demo and POC discussions.

They will be the best point of contact to address your specific requirements for EU data residency and regulatory compliance. Please feel free to share your briefing pack with them to help us prepare for the intro call.

In the meantime, you can check out more details here: https://www.atlassian.com/software/rovo/developers.

Best,
Samuil

[Arkadiusz Wroblewski]

Hello @Jarek Olchowik 

For a highly regulated EU bank like mBank, a deployment like this should go directly through Atlassian Sales or your account representative and not just the Community.

While your scenario fits Rovo Dev perfectly (generating code and creating draft PRs for human review), compliance is your main hurdle. Crucially, Atlassian notes that Rovo Dev does not currently support data residency, and it is limited to Bitbucket Cloud and GitHub.

You will need to validate this residency limitation, along with your specific SSO and audit logging requirements, directly with Atlassian before kicking off a POC. I have also flagged this thread so the right internal team can get eyes on it.

Best,

Arkadiusz🤠

[Hazrat Ullah]

Hi Jarosław,

This is a fascinating use case and exactly the kind of workflow many enterprise organizations are exploring as AI moves from simple assistance to autonomous software delivery. hear

The ability to go from a Jira issue to an AI-generated code fix and a Bitbucket pull request for human review has the potential to significantly accelerate development cycles while maintaining governance and compliance requirements. Your focus on EU data residency, auditability, SSO/SAML integration, and deployment flexibility is particularly relevant for regulated industries such as banking.

I hope the Atlassian team can connect with you directly, as feedback and real-world requirements from organizations operating at mBank's scale are invaluable for shaping enterprise-ready AI solutions. A 4–6 week proof of concept sounds like a great opportunity to evaluate not only the technical capabilities but also the governance, security, and operational aspects of the end-to-end workflow.

Looking forward to seeing how this discussion develops and hearing insights from both Atlassian and other enterprises evaluating similar agentic AI use cases.