Repository navigation
MIGRATION: Evaluate image and attachment handling #14513
Description
ASF Jira issues may have attached content, including images displayed inline in comments. This issue is a marker to evaluate how that content may migrate, and whether additional work may be required. Issue attachments may simply be referenced in an added comment, indicating attachments exist and can be retrieved from the source issue. Missing inline images (if not handled by migration) may be a bit more challenging to handle usefully.
Activity
toddfarmer commentedon Nov 14, 2022
By default, inline images render as broken image links in migrated content - see this example:
toddfarmer commentedon Nov 14, 2022
By adding some additional translation, it's possible to direct the inline image/attachment links in the migrated content back to the ASF Jira-hosted content. See this example.
Note that this points back to the original ASF Jira issue content, and the actual attachment has not been migrated to GitHub. This also means that if ASF Jira content is removed, inline content such as this will break.
toddfarmer commentedon Nov 14, 2022
There are currently 516 Jira issues with attachments.
toddfarmer commentedon Nov 14, 2022
It would be trivially easy to list the attachments with links to the content found in ASF Jira (not copying content into GitHub). Do we have strong feelings on needing to bring this referenced content over to GitHub itself, or can we allow migrated issues to point back to the content in ASF Jira? Because ASF Jira is world-readable, the content itself isn't restricted to registered Jira users. Any new attachments added would obviously end up in GitHub.
toddfarmer commentedon Nov 15, 2022
Unless there are objections, I plan to:
Both are demonstrated in this example issue: https://github.com/toddfarmer/test_import/issues/313
jorisvandenbossche commentedon Nov 16, 2022
Sounds good!