Repository navigation
Recover legacy Jira attachment metadata during file reads - #697
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The paired Jira migration file export stopped with
not_foundfor an existing, authorised attachment. Early imports can retain complete blob attributes without the laterattributes.v1marker or blob text relations. Recover that legacy Jira format when canonical blob text is absent, retaining text precedence and all existing actor checks.Seven focused retrieval tests pass, including owner read, unrelated-user denial, text precedence and unrelated/incomplete format rejection. A real read in the isolated restored Atlas snapshot retrieved the stopped file: 83,038 bytes with the exact retained SHA-256, without metadata or access changes. An adjacent artifact-ingestion suite was stopped during an unrelated database wait after eight passes; it is not a release gate for this read-path fix.
Von task: #V#task_agent_6bb01d1014e4b888a724b8e7ba2c77fe. Activation is limited to the authorised pinned migration runtime; no public web deployment or writer cutover.