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

Time entered for consumption and that saved does not match when time zone of the app and of system does not match #440

Open
ashika123 opened this issue Mar 3, 2015 · 2 comments
Assignees

Comments

@ashika123
Copy link

Steps:

  1. Let the app time zone be America/ New York
  2. Let the system time zone be Chennai/Kolkatta/Mumbai/New Delhi
    3.Save time for consumption as 10:45 am
    current Behaviour:Time gets saved as 12:15 am
    Expected behaviour:The selected time should match with the saved time.
@anujkhurana
Copy link

Why are we still discovering bugs? Is there any accountability of test team
or they can keep discovering new bugs and we must keep fixing them?

The only situation where reporting bugs at this stage is acceptable is when
these bugs got introduced in the last couple of updates. If this bug always
existed and the QA team missed it then I need to know when will I have a
final list of bugs from you.

On Tue, Mar 3, 2015 at 10:54 AM, ashika123 notifications@github.com wrote:

Steps:

  1. Let the app time zone be America/ New York
  2. Let the system time zone be Chennai/Kolkatta/Mumbai/New Delhi
    3.Save time for consumption as 10:45 am
    current Behaviour:Time gets saved as 12:15 am
    Expected behaviour:The selected time should match with the saved time.


Reply to this email directly or view it on GitHub
#440.

@ashika123
Copy link
Author

This issue had been reported previously #307
wasn't been completely fixed.

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

3 participants