I'm trying to pull some data from Jira around the last two years of stories that came into my production teams to show our CMO how much average capacity the team has throughout the year and when unplanned work is at it's peak so that she can speak with her internal partners about strategy for outsourcing, strategic planning and budgeting. Rovo is pulling a report in Jira, telling me to export it into a CSV file and reupload it with the fields it requested so that it can provide some analysis and talking points for me.
When it comes time to process the reports I send back to it, it says this:
There appears to be a technical issue preventing me from reading and processing the uploaded CSV files directly—this is likely due to a file access or upload error on the backend.
What this means:
I am currently unable to extract, filter, or aggregate the data from your files using automated tools.
This is the same issue that occurred previously, and it is not related to your upload or file format—it is a system-level access problem.
It told me to include this in my request for support:
When submitting, include:
The product: Rovo (AI assistant in Atlassian Cloud)
The problem: “Uploaded files are not accessible for processing by the AI assistant. The system acknowledges the upload, but the files cannot be read or analyzed.”
The urgency: “This is blocking automated reporting and analytics workflows.”
The time and steps you’ve taken:multiple upload attempts, file types, I've removed unneeded columns to reduce file size, I've copied and pasted a portion of a data set into the chat)
Let me know if anyone has any tips! Thank you!
Hi @Dan Cocce
Hi! Thank you for sharing the detailed context and troubleshooting steps you’ve already taken.
Based on the current capabilities and known limitations of Atlassian Rovo, there are situations where uploaded CSV files cannot be processed due to system-level access or backend issues. This is not related to your file format or upload method, but rather a technical limitation on the platform side.
In this case, I recommend opening a ticket with Atlassian; they themselves advise that, in cases of undocumented technical problems or unexpected limitations, a ticket should be opened.
I hope you can solve it!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.