Repository navigation
Review Jira losses and confirm mappings before apply - #2
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
1 participant
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.
Jira preview now gives one loss review shared by Settings, the CLI review file and the retained report. Every present concept shows row/value counts, retained originals and unresolved references. Status and priority suggestions require confirmation; assignees and sprints map only to existing native records. Attachment metadata remains visible and unfetched.
This is part 2 of the Jira file importer and depends on part 1. The generated 300-issue fixture proves positional repeated columns, exact review counts, ambiguous-date/missing-column refusal and unchanged database counts during preview. Existing erasure handles retained Jira author metadata. Mobile review tables scroll with keyboard access.
Validation: touched public-route tests, typecheck and source checks passed locally. The exact public candidate passed publication scanning with no new findings. No schema migration or Base refresh; real Jira exports remain unproven.
The shared collaboration browser check now waits for the exact unread row count within its existing five-second deadline. CI exposed a counter/list polling race; no assertion or time limit changed. The corrected desktop/mobile journey and independent check passed, and type/source checks and exact-tree publication scans passed on this head.