Honestly, Rovo Dev, this is completely unprofessional. On March 5th, you published an article (which has since been deleted: community.atlassian.com/forums/Rovo-articles/Updates-to-Rovo-Dev-access-and-credit-limits/ba-p/3202139) explaining that a payment method is now required to access the trial version. This update, useless for both you and us, completely messed everything up: all users are blocked right in the middle of their work. You can’t even use a simple backup to fix your mistakes without compromising users.
And let’s talk about your support. Some members of the Atlassian Team ask questions without ever listening to the answers. Users clearly explain that they haven’t used any credits, yet they still get the message “You’ve reached your Rovo Dev credit limit”, with screenshots to prove it.
And what does support do? They just ask generic questions or redirect to pages with updated rules. Seriously? The problem has never been the lack of a payment method it’s a bug in your platform, and you respond completely off-topic.
Even worse, asking for identifiers like the cloud ID in a public forum, even if some users gave consent, is a serious procedural mistake. This information should have been collected through a secure, private channel. Practices like this violate your own data protection commitments and put users at unnecessary risk...
Consider this a wake-up call: professionalism starts with listening and acting responsibly.
