Hey ya'll hey—this wasn’t expected trial behavior. Atlassian recently changed how Rovo Dev access and credits work, and there was also a bug during rollout that caused users to be blocked early (even below 2,000 credits). So this isn’t normal usage. @dangertest if it’s still happening, raise a support ticket with your cloudId—this needs a backend fix, not a config change.
Please read through this announcement: https://community.atlassian.com/forums/Rovo-articles/Updates-to-Rovo-Dev-access-and-credit-limits/ba-p/3202139
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @dangertest
not need for writing it all in Headings, which feels like an equivalent to Caps lock :) other users reported the same at the same time so there might have been a temporary hickup with the credits.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't. Does it still persist? Then opening a support request at support.atlassian.com would be advisable. They usually know of ongoing issues and current works on them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.