Hola Zishan,
Since the same issue and codebase work for some users but not others, I’d focus first on user-level access and feature enablement rather than the operating system or repository.
Ask an organization admin to compare one working user with one affected user in Atlassian Administration > Apps > AI settings > AI-enabled apps > Rovo Dev. Confirm that Live Preview is enabled at both the organization and site level, and check whether it’s listed as a limited beta feature. Limited beta access may not be available uniformly unless the organization has requested and received approval for that feature.
I’d also compare whether both users have the same Rovo Dev product role or group membership, particularly the Rovo Dev users group for the site, and whether either user has exhausted their Rovo Dev credit allowance. Atlassian notes that Rovo Dev can stop working when a user reaches the applicable credit limit.
If those settings match, could you clarify what the affected users actually see? For example, is the preview button missing entirely, present but disabled, or does it open and return an error? It’d also help to know whether this is the Jira-based Rovo Dev experience, the IDE extension, or another Rovo Dev interface, since “Live Preview” isn’t documented as a universal feature across all Rovo Dev surfaces.
At that point, I’d capture the account IDs of one user who is working and one who is failing, the site, browser, or IDE version, the exact timestamp, screenshots, and any console or network errors, and then raise it with Atlassian Support. The user-specific pattern could indicate a rollout, entitlement, or feature-flag issue that won’t be visible from the codebase itself.
Thanks,
James
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.