-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Issue - Backend
-
None
-
1
-
Severity 3 - Minor
Issue Summary
When cloning an issue via REST API attachments for cloned epic that are not going into the cloned issue's description field.
Steps to Reproduce
- Run REST API call to clone an epic which has attachment in the description field
- Clone fails - Error is thrown
Expected Results
Cloned issues created via REST API which include attachment links in the description field
Actual Results
traceId: 9a863c866da4580a
traceSampled: false
url: /rest/api/3/issue
...
message: Error when getting file metadata from collection: Failure{cause=null, reason=FILE_NOT_FOUND, retryAfter=null, message='{"error":{"code":"NotFoundError","title":"The file with the given id does not exist in collection \"upload-user-collection--724075332\"","href":"https://media.prod.atl-paas.net#NotFoundError"}}', httpStatusCode=404}
err: { [-]
class: [ [+]
]
msg: com.atlassian.jira.exception.RichTextBadInputException: error=ATTACHMENT_VALIDATION_ERROR
stack: cloud.atlassian.logmon.laas.api.PrivacySafeException: com.atlassian.jira.exception.RichTextBadInputException: error=ATTACHMENT_VALIDATION_ERROR
at com.atlassian.jira.util.text.RichTextFormatManagerImpl.lambda$tryCreateAttachmentWithFunc$54(RichTextFormatManagerImpl.java:1331)
at com.atlassian.jira.instrumentation.metrics.DefaultStatsDTimerService.time(DefaultStatsDTimerService.java:84)
Workaround
A possible workaround may be for the app in question to use the V2 APIs instead (which utilise Wikitext rather than ADF) as this does not have this limitation.