Token usage

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.

2 comments

Comment

@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.

Like • like this

Why did you cross out the word "issues"? Is that because of terminology changes in cloud or something? I'm still a DC admin, and it's still "issues" in my book.

Also, the AI bubble will pop soon. Atlassian is not the only ones using tokens for pricing. They probably don't want to explain it, as other companies don't want to admit AI isn't making anyone any money. The only people making money on AI right now are people selling you "How to use AI videos". lol

I watched a video where Uber claimed to use an entire year's worth of tokens in just two months.

Yes, Atlassian is changing wording to "Workitems" so this will be the Atlassian terminology for: tasks, issues, tickets, etc

Like • like this

I'm honestly surprised anyone gets any worthwhile use of Rovo. I have found it very lacking in even the simplest tasks. Returning 1/2 or incorrect information, or flat out failing to even respond. It can't even combine two confluence pages without choking. Rovo is still useless in my opinion and gets little use in my org. I'd be interested in hearing about any success stories someone may have.

My success story is that I created a free Gemini account and got a token for API. When I receive email from customer into our Jira (ServiceDesk) automation rule calls Gemini REST API and I get proper values for fields. No tokens no extra loadon backend no nothing.