After a failed import in the issue tracker, future successful attempts generate the same error message
After a failed import in the Bitbucket issue tracker, a future attempt that might be successful gives the same error message as the first failed attempt.
Steps to Reproduce
- Generate a zip file (let's call it file1.zip) from a Bitbucket issue tracker and download it to your machine
- Unzip the file in your machine and edit db-1.0.json so the JSON string in there is invalid
- Create a second zip file (file2.zip) from the folder that contains the invalid json
- Create a new repo in Bitbucket Cloud with an issue tracker
- Attempt to import file2.zip in the issue tracker of the new repo
- You should get a message "No db found in archive"
- Then, without leaving the Import & Export page, attempt to import file1.zip (which contains a .json file with valid json)
The import succeds and a message appears to confirm the succesful import
The import succeeds, however the user gets the same error message ("No db found in archive") as the one after the first failed attempt, which is misleading