Token usage

Kelly Reddy_1sgjv0

I do like using Rovo for work within our Atlassian environment, but with our team of 10 devs using it, Atlassian has not expanded its token usage capability and we would love to be a pilot user on that for them to predict and base pricing on! 🤗

it can handle more in depth work and come out with a more accurate resolution then Claude being connected, and plus doesn’t stop at the 100 ticket stoppage mark like Claude does by default. 

only thing you have to watch with Rovo is the actionable implementation of the work, as another user said - it can be unpredictable & unreliable. 

s_gridnevskii

@Kelly Reddy our instance has 250k issues sorry workitems since 2015 and I think our Rovo tokens will fly away like sand between fingers. This is really a big problem and we all wait for explanation from Atlassian. I can understand their logic. Every request to jira backend consumes $$$ and agents generate hundreds of requests. If Rovo allows unlimited access without limitation Atlassian will go bankrupt in a couple of months. But not explaining it is a kind of hypocricy.

I see solution in separating our big Jira instance into 10-15 smaller ones with a limited number of users in each of them. And making automations to copy data from one instance to another. It may be more cost efficient especially taking into considetation that not all users need all plugins and features.