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.

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

Closed
carlosvirreira opened this issue Mar 7, 2024 · 14 comments · Fixed by #836
Closed
Assignees
Labels
enhancement New feature or request Priority: High Issues that are with very high priority User requested feature

Comments

@carlosvirreira
Copy link
Contributor

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:

  1. Stop what I am doing and wait for my labels
  2. Create all my assets and then order labels

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

@DonKoko
Copy link
Contributor

DonKoko commented Mar 8, 2024

@jurrejansen @carlosvirreira do we have a design for this? I thought we did but I don't remember where to find it.

@jurrejansen
Copy link

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

Screenshot 2024-03-08 at 10 13 26

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.

https://www.figma.com/file/oBSRWYlWtjlLwu39LtpMHS/Shelf-%7C-FigJam?type=whiteboard&node-id=0%3A1&t=NS9UefEGJgxeqlK4-1

Screenshot 2024-03-08 at 10 15 32

@jurrejansen
Copy link

Hi @DonKoko here's the scenario, let me know if anything is unclear.

https://www.figma.com/file/ykvc0MhPeNLsrJ4tJsKosQ/Shelf-%7C-UX-Scenarios?type=design&node-id=4199-41708&mode=design

@carlosvirreira
Copy link
Contributor Author

Very clear to me - great enhancement.

@DonKoko
Copy link
Contributor

DonKoko commented Mar 27, 2024

@carlosvirreira @jurrejansen this is deployed on testapp and ready to be tested.
1 small note. We have a different bug related to vite that breaks the asset page if there is a location of the last scan. Please dont give your browser location permissions when testing this feature so it doesn't break the asset.

Some testing recommendations:

  1. To to admin panel
  2. Find your user and click on any org
  3. Generate some orphan codes and click the code id
  4. That will trigger the process

@DonKoko DonKoko self-assigned this Mar 27, 2024
@DonKoko DonKoko added enhancement New feature or request Priority: High Issues that are with very high priority labels Mar 27, 2024
@jurrejansen
Copy link

jurrejansen commented Mar 27, 2024

FEEDBACK

  • The built in scanner does not work for orphaned codes
RPReplay_Final1711536889.MP4
  • I think we should remove section with the Shelf logo as it is taking up some much needed screen real estate. I know this is an easy way to get back to the main part of the app but still. They can choose 'Close' and back out from there

Screenshot 2024-03-27 at 12 33 52

  • Can we decrease font size of the heading to match design (18px / 1.25rem)

  • Can we change copy heading into: Link with existing asset

  • Can we change copy of sub text into: Choose an asset to link with this QR tag.

  • Can we add the border lines separating the different sections of the modal / page

  • Can we have to border lines taking up the full width of the screen

Screenshot 2024-03-27 at 13 07 16

  • Any way we can avoid the browser UI covering the fixed footer that contains the 'Close' button. For example, this doesn't happen with the Manage assets modal for bookings on mobile.

QUESTIONS

@DonKoko @carlosvirreira

  • 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
  • Do we need need to show the status of an asset here? There's not really a downside to it i guess

@carlosvirreira
Copy link
Contributor Author

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.

@DonKoko
Copy link
Contributor

DonKoko commented Mar 28, 2024

One more point to add:

  • the quick actions after scanning a qr seem to be broken on dev branch. Happens both with in-app scanner and camera app

@DonKoko
Copy link
Contributor

DonKoko commented Apr 1, 2024

the quick actions after scanning a qr seem to be broken on dev branch. Happens both with in-app scanner and camera app

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

@DonKoko
Copy link
Contributor

DonKoko commented Apr 1, 2024

The built in scanner does not work for orphaned codes

@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.
Screenshot 2024-04-01 at 14 41 25

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.

@DonKoko
Copy link
Contributor

DonKoko commented Apr 1, 2024

@jurrejansen all the changes are deployed to testapp. Please test again and lmk if we are ready to go live.

@jurrejansen
Copy link

jurrejansen commented Apr 2, 2024

@DonKoko Some minor stuff

  • Change copy from "Link with existingasset" -> "Link with existing asset"
  • Missed it last time, would it be a hassle to add the Location filter in this component? This also applies to the Manage assets modal for bookings
RPReplay_Final1712044228.MP4
  • Top border of footer section isn't full width
  • Header section isn't separated by a border

Any way we can avoid the browser UI covering the fixed footer that contains the 'Close' button. For example, this doesn't happen with the Manage assets modal for bookings on mobile.

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
  • Let's always call it 'asset' instead of 'item' for consistency

IMG_1536


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

Screenshot 2024-04-02 at 10 19 36

@DonKoko
Copy link
Contributor

DonKoko commented Apr 2, 2024

@jurrejansen deployed to testapp.

Missed it last time, would it be a hassle to add the Location filter in this component? This also applies to the Manage assets modal for bookings

Nowadays its easy so I added it no problem.

@jurrejansen
Copy link

@DonKoko nice, all seems good to me. Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Priority: High Issues that are with very high priority User requested feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants