See e.g. T9757.
Not much of an issue as long as old-bugzilla is up, but we should avoid irretrievably losing those patches. A patch can be marked obsolete by mistake, it might be an abandoned old attempt that can still help to inform the next attempt etc.
Attachments marked as "private" or as "obsolete" in Bugzilla will not be migrated. I'm afraid this is nothing that we can fix anymore after the migration.
Please provide an example of a patch in Bugzilla marked as obsolete by mistake.
Not much of an issue as long as old-bugzilla is up, but we should avoid irretrievably losing those patches.
Description of T1198: Bugzilla HTML static version and database dump edited to make this requirement explicit. I will merge this task there.
providing the database dump is still a blocker to shut down old-bz even if those missing attachments had been migrated. if the decision was not to migrate them that would be unrelated
We won't migrate obsolete attachments from Bugzilla to Phabricator.
That's how I read the task summary and hence proposing "declined" status here.
Will the obsolete attachments be included in the database dump? If so, the task of extracting them can be done by anyone with a specific need, and this task can be closed IMO.
One sanity check might be open bugs (as at migration) with only obsolete patches - I see that occasionally.
They will not be included as the upstream "sanitize" script removes them. T85141 includes the output line
Removing attachment data to preserve disk space...