Duplicated media IDs are breaking the new issue view

Summary

We're seeing cases where media_store_id for attachments in issues (the ID that Jira service media.api attributes to files throughout Atlassian Products, i.e: Attachments) is being duplicated. When this happens, the new issue view (only) fails to load and throws an error in the network to help diagnosing:

The problem happens if the attachment with duplicate ID is added to the issue's description (and possibly other fields) in the old issue view, for example, using this: !image.png|thumbnail! and is then shown in the new issue view.

If the attachment with duplicate ID is added to a comment, the issue opens, but no comment is shown, even the ones that do not contain the attachment.

Steps to Reproduce

We were not able to have the duplicated ID, but whenever it does

1. Have an issue with an attachment with duplicate Media API ID
2. Add a thumbnail of that image to a description or a comment
3. Try to load the issue in the new issue view

Expected Results

Load the issue (we should handle the duplicated situation, or media_store_id shouldn't be a PK)

Actual Results

Attachment in description
The issue doesn't load, it throws a UI generic error like:

Attachment in comments
The issue loads, but we cannot see any comments. No error appears in UI, it just shows an issue without comments.

Workaround

1. Check the .event property from the error thrown, you'll find the filenames with duplicate ID
2. Check the ticket in old issue view
3. Download the attachment
4. Delete the attachment from the ticket
5. Add it back again
   This workaround resets the author (to you) and the date (to now) of the attachment. If this metadata is important to you, don't follow this workaround

or

• Disable the new Issue View (can Be done by adding '?oldIssueView=true' to the issue URL i.e: instance.atlassian.net/browse/ABC-123?oldIssueView=true // or by disabling it: Profile Picture -> Personal Settings -> Turn off the switch)