Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Existing barcodes from OG gets lost after migration #4272

Open
nishaDangol-Sussol opened this issue Jun 25, 2024 · 1 comment
Open

Existing barcodes from OG gets lost after migration #4272

nishaDangol-Sussol opened this issue Jun 25, 2024 · 1 comment
Labels
bug Something is borken Migrate Existing Desktop Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release Team Ruru 🦉 Carl, Andrei, Roxy

Comments

@nishaDangol-Sussol
Copy link

What went wrong? 😲

Existing barcodes from OG gets lost after migration

Expected behaviour 🤔

barcodes should not get lost like that

How to Reproduce 🔨

Steps to reproduce the behaviour:

  1. HAve a OG remote desktop site with some barcodes (Add barcodes to existing lines if needed in OG)
  2. Sync
  3. Now migrate that OG desktop to oms, i.e., reset hardware ID and reinitialise
  4. Login to newly migrated oms store
  5. See those stocks
  6. See error: the barcode value is lost

Your environment 🌱

  • Open mSupply Version: v2.1.0-rc3
  • Legacy mSupply Central Server Version: v7-15-06
  • Platform: apk, browser(chrome)
  • Database type: sqlite
@nishaDangol-Sussol nishaDangol-Sussol added bug Something is borken needs triage Severity: Normal Bugs which have an acceptable workaround. Moderate/tolerable user impact. Next minor release. needs daily triage New bug to be triaged by the release team Migrate Existing Desktop labels Jun 25, 2024
@nishaDangol-Sussol nishaDangol-Sussol mentioned this issue Jun 25, 2024
Closed
72 tasks
@andreievg andreievg added Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release and removed needs daily triage New bug to be triaged by the release team needs triage Severity: Normal Bugs which have an acceptable workaround. Moderate/tolerable user impact. Next minor release. labels Jun 27, 2024
@andreievg andreievg added this to the V2.2.0 milestone Jun 27, 2024
@andreievg
Copy link
Collaborator

Triage, don't really have to for hot fix, because it might be quite time consuming to fix, but intending to look at it early 2.2

@mark-prins mark-prins modified the milestones: V2.2.0, Carryover Jun 27, 2024
@andreievg andreievg added the Team Ruru 🦉 Carl, Andrei, Roxy label Jul 1, 2024
@andreievg andreievg removed this from the V2.2.0 milestone Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something is borken Migrate Existing Desktop Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release Team Ruru 🦉 Carl, Andrei, Roxy
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mark-prins @andreievg @nishaDangol-Sussol