I am having the same problem which also extends to other report writers being unable to amend reports writen by others as JS overwrites the report on upload. I have received the following workaround, not tried it though; Assuming that the Jasper repository is in an Oracle database (as opposed to postgreSQL), a workaround is to delete all rows from the 'jiaccessevent' table prior to importing the reports. We ran into this issue a couple weeks back when we were troubleshooting the LRP report issue with BAE. The way we worked around it then was to reload the Japser repository completely... but obviously that's not ideal. Deleting from the 'jiaccessevent' table is less intrusive. From what I've been able to figure out, this is just an auditing table that sits between the user table, and the 'jiresource' table. From what I can tell is it just keeps track of who viewed/touched what report, and when