-
Notifications
You must be signed in to change notification settings - Fork 193
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.
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
[Feature request]: Create a flow to link an 'unclaimed tag' to an existing asset #829
Comments
@jurrejansen @carlosvirreira do we have a design for this? I thought we did but I don't remember where to find it. |
Hi @DonKoko there are very old designs here https://www.figma.com/file/2XkiKJ4II7Mux6JJL9hYTm/Shelf-App-%7C-Production-Ready?type=design&node-id=6267-340162&mode=design But I think they need to be revisited. Are you planning to work on this in the near future? Also I think this concept needs to be added to the flowchart of scanning logic. |
Hi @DonKoko here's the scenario, let me know if anything is unclear. |
Very clear to me - great enhancement. |
@carlosvirreira @jurrejansen this is deployed on testapp and ready to be tested. Some testing recommendations:
|
FEEDBACK
RPReplay_Final1711536889.MP4
QUESTIONS
|
Hi @jurrejansen good report: Do we really need the 'Status' filter when linking a code to existing asset? Personally think the extra screen real estate by removing it preferable I'd say no. However, I do believe that the approach here was to ship a v1 fast. I would rather have something that is 90% good out there and solves the problem than spending a ton of time over-polishing. The rest of the content/language changes are highly appreciated. |
One more point to add:
|
This is caused by the vite update. I am now deploying to testapp without vite to double confirm it. Also mentioned in #882 EDIT: Confirmed thats the reason |
@jurrejansen Man I spent like 5h testing this and it was so stupid. Its just because you are trying to scan it via preview on the mac. And the way we made the app "print" the codes is without white space around them. Based on the QR spec this white space is kinda required. We just did it like this because of our process of placing them on sheets and printing them. I made 1 code with whitespace around it and it instantly worked. So I think the only thing we have to know about this is to actually inform our users who ask us to send them orphaned codes that the codes need at least like 5-10px white space on each side so the scanner can recognize them. Another option is that I just add some margin already to the QR code and you will need to adjust your template. |
@jurrejansen all the changes are deployed to testapp. Please test again and lmk if we are ready to go live. |
@DonKoko Some minor stuff
RPReplay_Final1712044228.MP4
For me this still happens, the footer with Close button is hidden behind browser UI. Not sure how many users will get confused by this and there's always the Previous button from the browser they could use. However, for Manage assets modal this doesn't happen. RPReplay_Final1712044826.MP4
Yeah I guess it's best to bake in the whitespace then. Something like the screenshot down below, not too much. I tested again and now I was able to scan an orphaned code via the mac preview for some reason. RPReplay_Final1712045840.MP4 |
@jurrejansen deployed to testapp.
Nowadays its easy so I added it no problem. |
@DonKoko nice, all seems good to me. Closing |
Contact Details
No response
Is your feature request related to a problem? Please describe?
As a user, if I am trying to get labels from the Shelf team - I mostly have to either:
Describe the solution you'd like
Ideally I can order shelf asset tags and when scanning I can pick either to link them to an existing asset or create a brand new asset.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: