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

Tracking reminder time limits are not being respected #1383

Closed
tcrammond opened this issue Apr 16, 2019 · 1 comment · Fixed by #1384
Closed

Tracking reminder time limits are not being respected #1383

tcrammond opened this issue Apr 16, 2019 · 1 comment · Fixed by #1384
Assignees

Comments

@tcrammond
Copy link
Contributor

  • OS version: *
  • Browser version: *
  • Extension version: 1.30

🐛 Describe the bug

The "Remind me to track time" notification will run outside of the set work hours.

Expected behaviour

It does not run outside of the set work hours.

Other details or context

Intercom 21464735863

@tcrammond tcrammond added the bug label Apr 16, 2019
@tcrammond tcrammond self-assigned this Apr 16, 2019
tcrammond added a commit that referenced this issue Apr 16, 2019
This had broken due to a mistake with an async change to a function. Fixes #1383.
tcrammond added a commit that referenced this issue Apr 17, 2019
This had broken due to a mistake with an async change to a function. Fixes #1383.
shantanuraj pushed a commit that referenced this issue Apr 23, 2019
This had broken due to a mistake with an async change to a function. Fixes #1383.
toggl-button-bot added a commit that referenced this issue Apr 23, 2019
## [1.30.3](1.30.2...1.30.3) (2019-04-23)

### Bug Fixes

* Fix tracking reminder not respecting working hours ([979177d](979177d)), closes [#1383](#1383)
@toggl-button-bot
Copy link
Collaborator

🎉 This issue has been resolved in version 1.30.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging a pull request may close this issue.

2 participants