-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Backup & Restore - Import From JIRA Cloud
-
4
-
Severity 2 - Major
Problem Description
Not all customers are affected
The new issue view that relies on getting metadata from the Media store for display and for download link. If an instance done attachment import before, likelihood that it will replace the attachment name with the directory instead, causing discrepancy when viewing issue using this new feature.
This is due to during attachment import, it populates the metadata with the directory order instead of the actual name of the file.
"name": "attachments\/EXAMPLE\/10000\/EXAMPLE-577\/12345",
The expected result should be:
"name": "filename.docx",
This has caused the attachments to be viewed as ID and downloaded as ID instead of it's actual filename on the new issue view.
Steps to replicate
- At one issue, attach a new file, fetch the metadata from Media. Noticed that the name is stored as the filename
- Run attachment import for the same file
- Noticed that media will recreate a new file id and fetching the metadata will have the name stored as the directory order
This is not visible to customers, and only through internal tools we are able to retrieve this information
Workaround
Switch back to old issue view by turning off the new issue view from user profile
- is duplicated by
-
JRACLOUD-69656 Server to Cloud migrated attachments are not displaying their right names in the New JIRA Issue View but ok in the Issue Navigator
-
- Closed
-
- is related to
-
MIG-1137 After migrating to Jira Cloud some attachments are not properly displayed in the new Jira issue view
-
- Closed
-