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

[GAT-BEI003-5] Oder history doesn't show date and time and "ASAP-Being Prepped" is display if ordering with default ETA #503

Open
gatgithub opened this issue Feb 1, 2016 · 1 comment

Comments

@gatgithub
Copy link

Issue No: 5
Device: iPhone 6/iOS 8.4

Affected Component(s)

  • Settings / Profile

Bug Description

Grey Area (Unknown Expected Behaviour)

ACTUAL RESULTS:-
Oder history doesn't show date and time and will result to ASAP-Being Prepped!

EXPECTED RESULTS:-
Order history should display the full details including time and date of order, and also as per the tester spec it is mentioned that "Added a new screen for viewing order history based on date, time and amount spent. accessible from settings screen and order confirmation screen"

OTHER NOTES / ERROR MESSAGES:-
Note:
It is observed that this issue occur if your don't modify the delivery schedule located at the "Today's Lunch" header with drop down menu.
Email:[email protected]/Password admin1234

Version 2.66

http://bugs8.gatserver.com/uploads/87ce9b267563eb8def81df39fcb85fab.mp4


Reproduction Steps

  • Open the app
  • Login using your credentials
  • Tap main dish and side dish to add
  • Tap place an order
  • Enter credit card details
  • Tap let's eat
  • Tap settings menu
  • Tap orders
  • Observe the order history
@gatgithub gatgithub added this to the 2.65 [previous] milestone Feb 1, 2016
@gatgithub gatgithub removed this from the 2.65 [previous] milestone Feb 1, 2016
@vcardillo vcardillo added UX and removed bug labels Feb 1, 2016
@vcardillo
Copy link
Member

So this is actually a UX misunderstanding, and not a bug. The user opted to order "ASAP", from our on demand service, instead of scheduling ahead. Everything worked as expected, but the user was confused. So we'll have to think about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants