Status Update
Comments
be...@gmail.com <be...@gmail.com> #2
Or at least integrate it in the FreeBusy query response, to take the working hours into consideration.
be...@shepherd.com <be...@shepherd.com> #3
[Deleted User] <[Deleted User]> #4
ir...@gmail.com <ir...@gmail.com> #5
ja...@jis.edu.bn <ja...@jis.edu.bn> #6
[Deleted User] <[Deleted User]> #7
ed...@newrelic.com <ed...@newrelic.com> #8
* computing pager fatigue on our teams
* adjusting alert activation thresholds to reduce imposition on work-life balance.
* support tooling around scheduling and planning conversations across time zones
ro...@nielsen.com <ro...@nielsen.com> #9
st...@ostec.de <st...@ostec.de> #10
do...@tryroots.io <do...@tryroots.io> #11
pf...@enova.com <pf...@enova.com> #12
an...@thinkingbytes.net <an...@thinkingbytes.net> #13
[Deleted User] <[Deleted User]> #14
sr...@gmail.com <sr...@gmail.com> #15
da...@notionoutreach.com <da...@notionoutreach.com> #16
Further love that we're still +1-ing things in 2019. 👍🏼 (+1)
[Deleted User] <[Deleted User]> #17
[Deleted User] <[Deleted User]> #18
st...@gmail.com <st...@gmail.com> #19
ad...@why-studio.com <ad...@why-studio.com> #20
df...@gmail.com <df...@gmail.com> #21
sh...@ocado.com <sh...@ocado.com> #22
I would echo the comment above that suggests this would make sense as part of the freebusy API, perhaps some optional parameter that indicates that you want the working hours to also be checked against?
va...@gmail.com <va...@gmail.com> #23
sh...@ocado.com <sh...@ocado.com> #24
Again, it completely devalues the functionality if internally built applications or 3rd party applications (e.g. Calendly) aren't able to access this information.
mi...@donut.ai <mi...@donut.ai> #25
kn...@gmail.com <kn...@gmail.com> #26
ly...@gmail.com <ly...@gmail.com> #27
+1 +1 +1
on...@gmail.com <on...@gmail.com> #28
[Deleted User] <[Deleted User]> #29
ol...@gmail.com <ol...@gmail.com> #30
ga...@gmail.com <ga...@gmail.com> #31
va...@gmail.com <va...@gmail.com> #32
[Deleted User] <[Deleted User]> #34
[Deleted User] <[Deleted User]> #35
[Deleted User] <[Deleted User]> #36
ju...@scurri.com <ju...@scurri.com> #37
yo...@gmail.com <yo...@gmail.com> #38
[Deleted User] <[Deleted User]> #39
[Deleted User] <[Deleted User]> #40
ji...@gmail.com <ji...@gmail.com> #41
ca...@google.com <ca...@google.com>
ad...@googlemail.com <ad...@googlemail.com> #42
na...@gmail.com <na...@gmail.com> #43
jp...@gmail.com <jp...@gmail.com> #44
an...@madewithlove.com <an...@madewithlove.com> #45
ja...@shuttlecloud.com <ja...@shuttlecloud.com> #46
It's very difficult, correction: impossible, to design products that take wellbeing into consideration when there's no way to know the working hours of an individual.
I'd like to remind the Google Calendar API team the following quotes from the Wellbeing website (
----------------
“We want to help people find the right balance and gain a sense of digital wellbeing.”
Sundar Pichai, May 2018 <------ May 2018!!!!!!!!
Optimizing our products.
We have launched a longitudinal study to better understand the effectiveness of our digital wellbeing tools in helping people achieve greater balance in their tech use. These findings will help us optimize our current offerings while inspiring brand new tools.
Inspiring designers and developers to create new tools.
We've launched Digital Wellbeing Experiments to inspire designers and developers to explore new ways of integrating digital wellbeing into their creations.
OUR ONGOING COMMITMENT
We’re working to ensure all of our products support your digital wellbeing.
---------------
Please, in the future, make sure that any wellbeing related feature is available through the API. WH is available internally for Google products but not exposed via the API for third party developers. :-(
Bad Google... ;-)
is...@google.com <is...@google.com>
[Deleted User] <[Deleted User]> #47
Are there any plans on exposing this functionality? If so, what is the internal status?
mi...@donut.ai <mi...@donut.ai> #48
[Deleted User] <[Deleted User]> #49
[Deleted User] <[Deleted User]> #50
[Deleted User] <[Deleted User]> #51
pe...@pik.ru <pe...@pik.ru> #52
pe...@gmail.com <pe...@gmail.com> #53
ni...@morrisonsplc.co.uk <ni...@morrisonsplc.co.uk> #54
yu...@expensify.com <yu...@expensify.com> #55
el...@temp.prelude.co <el...@temp.prelude.co> #56
el...@snyk.io <el...@snyk.io> #57
ge...@snyk.io <ge...@snyk.io> #58
va...@temp.prelude.co <va...@temp.prelude.co> #59
ni...@temp.prelude.co <ni...@temp.prelude.co> #60
ky...@temp.prelude.co <ky...@temp.prelude.co> #61
ha...@temp.prelude.co <ha...@temp.prelude.co> #62
[Deleted User] <[Deleted User]> #63
ra...@gmail.com <ra...@gmail.com> #64
di...@snyk.io <di...@snyk.io> #65
gf...@gmail.com <gf...@gmail.com> #66
ge...@snyk.io <ge...@snyk.io> #67
cr...@snyk.io <cr...@snyk.io> #68
la...@snyk.io <la...@snyk.io> #69
ch...@snyk.io <ch...@snyk.io> #70
ge...@gmail.com <ge...@gmail.com> #71
ca...@snyk.io <ca...@snyk.io> #72
[Deleted User] <[Deleted User]> #73
[Deleted User] <[Deleted User]> #74
[Deleted User] <[Deleted User]> #75
[Deleted User] <[Deleted User]> #76
[Deleted User] <[Deleted User]> #77
zh...@gmail.com <zh...@gmail.com> #78
ma...@gmail.com <ma...@gmail.com> #79
09...@gmail.com <09...@gmail.com> #80
Are there any plans on exposing this functionality? If so, what is the internal status?"
Get the internal status of a Google project, good one Seriously, doing calculation with calendar data would be great. Thanks +1
cr...@iol.unh.edu <cr...@iol.unh.edu> #81
Another use case would be the ability to dynamically set working hours. Since right now it's an every MWF or whatever days but would be nice to be able to set it per date. I could do this easily with a script if the api exposed a get and set for this feature.
[Deleted User] <[Deleted User]> #82
os...@codesandbox.io <os...@codesandbox.io> #83
mi...@doit.com <mi...@doit.com> #84
[Deleted User] <[Deleted User]> #85
po...@msu.edu <po...@msu.edu> #86
vv...@purestorage.com <vv...@purestorage.com> #87
[Deleted User] <[Deleted User]> #88
[Deleted User] <[Deleted User]> #89
jd...@joinhandshake.com <jd...@joinhandshake.com> #90
mc...@joinhandshake.com <mc...@joinhandshake.com> #91
mm...@joinhandshake.com <mm...@joinhandshake.com> #92
ky...@temp.prelude.co <ky...@temp.prelude.co> #93
[Deleted User] <[Deleted User]> #94
em...@aetion.com <em...@aetion.com> #95
sc...@aetion.com <sc...@aetion.com> #96
ke...@rezi.co <ke...@rezi.co> #97
av...@gmail.com <av...@gmail.com> #98
am...@gcp.segment.com <am...@gcp.segment.com> #99
ka...@collibra.com <ka...@collibra.com> #100
jd...@bellese.io <jd...@bellese.io> #101
de...@stitchfix.com <de...@stitchfix.com> #102
ta...@stitchfix.com <ta...@stitchfix.com> #103
ma...@daily-harvest.com <ma...@daily-harvest.com> #104
ra...@expensify.com <ra...@expensify.com> #105
mi...@gmail.com <mi...@gmail.com> #106
[Deleted User] <[Deleted User]> #107
[Deleted User] <[Deleted User]> #108
[Deleted User] <[Deleted User]> #109
fa...@backbase.com <fa...@backbase.com> #110
[Deleted User] <[Deleted User]> #111
[Deleted User] <[Deleted User]> #112
[Deleted User] <[Deleted User]> #113
[Deleted User] <[Deleted User]> #114
[Deleted User] <[Deleted User]> #115
re...@gmail.com <re...@gmail.com> #116
re...@backbase.com <re...@backbase.com> #117
[Deleted User] <[Deleted User]> #118
ap...@cloudflare.com <ap...@cloudflare.com> #119
dr...@cloudflare.com <dr...@cloudflare.com> #120
[Deleted User] <[Deleted User]> #121
[Deleted User] <[Deleted User]> #122
ro...@wepay.com <ro...@wepay.com> #123
bf...@vitas.ai <bf...@vitas.ai> #124
vs...@gmail.com <vs...@gmail.com> #125
[Deleted User] <[Deleted User]> #126
Good lord, get to it already! How hard could it be??
re...@gmail.com <re...@gmail.com> #127
[Deleted User] <[Deleted User]> #128
jo...@redbooth.com <jo...@redbooth.com> #129
yu...@gmail.com <yu...@gmail.com> #130
cr...@mongodb.com <cr...@mongodb.com> #131
+1
[Deleted User] <[Deleted User]> #132
bo...@gmail.com <bo...@gmail.com> #133
mk...@wanadev.fr <mk...@wanadev.fr> #134
[Deleted User] <[Deleted User]> #135
[Deleted User] <[Deleted User]> #136
[Deleted User] <[Deleted User]> #137
na...@natedesmond.com <na...@natedesmond.com> #138
jo...@oikos-international.org <jo...@oikos-international.org> #139
mi...@microvet.co.za <mi...@microvet.co.za> #140
jg...@gmail.com <jg...@gmail.com> #141
a....@dodobrands.io <a....@dodobrands.io> #142
ma...@unity3d.com <ma...@unity3d.com> #143
su...@justin.tv <su...@justin.tv> #144
mi...@gmail.com <mi...@gmail.com> #145
ar...@getduos.com <ar...@getduos.com> #146
[Deleted User] <[Deleted User]> #147
[Deleted User] <[Deleted User]> #148
[Deleted User] <[Deleted User]> #149
ed...@panoramaed.com <ed...@panoramaed.com> #150
[Deleted User] <[Deleted User]> #151
mi...@google.com <mi...@google.com> #152
Hello,
Implementing this feature is currently not a priority. Therefore, I'll proceed to close this.
Kind regards.
ni...@gmail.com <ni...@gmail.com> #153
ar...@gohuddl.com <ar...@gohuddl.com> #154
It'd be nice to be able to take working hours into account in Freebusy request
[Deleted User] <[Deleted User]> #155
mi...@microvet.co.za <mi...@microvet.co.za> #156
Is there another way to achieve the same functionality?
[Deleted User] <[Deleted User]> #157
[Deleted User] <[Deleted User]> #158
ok...@navan.com <ok...@navan.com> #159
er...@happyhorizon.com <er...@happyhorizon.com> #160
ad...@gmail.com <ad...@gmail.com> #161
vi...@modernloop.io <vi...@modernloop.io> #162
ja...@gmail.com <ja...@gmail.com> #163
[Deleted User] <[Deleted User]> #164
ro...@gmail.com <ro...@gmail.com> #165
er...@gmail.com <er...@gmail.com> #166
te...@surplace.co <te...@surplace.co> #167
xd...@gmail.com <xd...@gmail.com> #168
I really really hope that today's announcement of enhanced working hours[1] means Google's finally going to make this status available via the Google Calendar API. 🤞
[Deleted User] <[Deleted User]> #169
[Deleted User] <[Deleted User]> #170
sa...@mongodb.com <sa...@mongodb.com> #171
gi...@block.xyz <gi...@block.xyz> #172
This is essential to our new "distributed workforce" initiatives
[Deleted User] <[Deleted User]> #173
For everyone still commenting on this issue after it has been marked obsolete, may I suggest trying to star and bump
yu...@pwc.com <yu...@pwc.com> #174
re...@gladly.com <re...@gladly.com> #175
[Deleted User] <[Deleted User]> #176
[Deleted User] <[Deleted User]> #177
k....@smartrecruiters.com <k....@smartrecruiters.com> #178
k....@smartrecruiters.com <k....@smartrecruiters.com> #179
sh...@herp.co.jp <sh...@herp.co.jp> #180
ro...@wise.com <ro...@wise.com> #181
al...@stitchfix.com <al...@stitchfix.com> #182
[Deleted User] <[Deleted User]> #183
vf...@thoughtworks.com <vf...@thoughtworks.com> #184
jo...@redbooth.com <jo...@redbooth.com> #185
pa...@interviewplanner.com <pa...@interviewplanner.com> #186
mp...@virtuslab.com <mp...@virtuslab.com> #187
[Deleted User] <[Deleted User]> #188
[Deleted User] <[Deleted User]> #189
mi...@flatiron.com <mi...@flatiron.com> #190
ka...@flatiron.com <ka...@flatiron.com> #191
[Deleted User] <[Deleted User]> #192
mi...@mikewoodld.com <mi...@mikewoodld.com> #193
ba...@airtable.com <ba...@airtable.com> #194
mi...@factorial.io <mi...@factorial.io> #195
id...@zoominfo.com <id...@zoominfo.com> #196
am...@fellow.co <am...@fellow.co> #197
sa...@goodtime.io <sa...@goodtime.io> #198
lo...@nylas.com <lo...@nylas.com> #199
st...@nielsen.com <st...@nielsen.com> #200
[Deleted User] <[Deleted User]> #201
ya...@sureapp.com <ya...@sureapp.com> #202
my...@openupmedia.be <my...@openupmedia.be> #203
s....@sensory-minds.com <s....@sensory-minds.com> #204
an...@lyft.com <an...@lyft.com> #205
de...@savvycal.com <de...@savvycal.com> #206
co...@gmail.com <co...@gmail.com> #207
[Deleted User] <[Deleted User]> #208
ck...@gmail.com <ck...@gmail.com> #209
ge...@gmail.com <ge...@gmail.com> #210
ap...@cloudflare.com <ap...@cloudflare.com> #211
[Deleted User] <[Deleted User]> #212
na...@demo.mbfcorp.com <na...@demo.mbfcorp.com> #213
an...@verizon.com <an...@verizon.com> #214
Since this one was closed, I opened a new request:
I also have a few questions/comments on Google's behavior.
- If enough users are asking for the feature, then why is it not a priority?
- Even if it is not a priority right now, why close the request? Leave it open so that it can be implemented when it can be a priority. If Google closes it then folks won't vote on it. But if Google leaves it open then folks can vote on it and Google will see much of a priority it is for their customers. Or is Google saying they don't care about customer needs?
td...@stripe.com <td...@stripe.com> #215
It also looks like 198667127 is missing a reporter and doesn't allow comments. Is it the age of this feature request that was a problem? Please provide some clarity on this.
be...@stripe.com <be...@stripe.com> #216
oi...@gmail.com <oi...@gmail.com> #217
le...@one-line.com <le...@one-line.com> #218
tm...@mediality.com.au <tm...@mediality.com.au> #219
su...@wesang.com <su...@wesang.com> #220
da...@helloalma.com <da...@helloalma.com> #221
rf...@gmail.com <rf...@gmail.com> #222
lo...@coalitioninc.com <lo...@coalitioninc.com> #223
Working Hours != Working Location.
ju...@cloudpilots.com <ju...@cloudpilots.com> #224
+1
jo...@gmail.com <jo...@gmail.com> #225
ma...@getclockwise.com <ma...@getclockwise.com> #226
si...@agilebits.com <si...@agilebits.com> #227
yu...@gmail.com <yu...@gmail.com> #228
ja...@rooftek.com <ja...@rooftek.com> #229
st...@steegle.com <st...@steegle.com> #230
an...@verizon.com <an...@verizon.com> #231
That API does not mention it will include working hours.
jo...@colpal.com <jo...@colpal.com> #232
ni...@gmail.com <ni...@gmail.com> #233
za...@outschool.com <za...@outschool.com> #234
li...@samsara.com <li...@samsara.com> #235
na...@gmail.com <na...@gmail.com> #236
[Deleted User] <[Deleted User]> #237
[Deleted User] <[Deleted User]> #238
ma...@ninjatech.ai <ma...@ninjatech.ai> #239
Some people might not willing to have meetings even during some certain working hours.
ja...@rooftek.com <ja...@rooftek.com> #240
st...@chino.io <st...@chino.io> #241
mi...@getclockwise.com <mi...@getclockwise.com> #243
sb...@google.com <sb...@google.com>
tr...@gmail.com <tr...@gmail.com> #244
ro...@jouwweb.nl <ro...@jouwweb.nl> #245
The weird thing is that the
[Deleted User] <[Deleted User]> #246
ra...@mongodb.com <ra...@mongodb.com> #247
ta...@tractioncomplete.com <ta...@tractioncomplete.com> #248
jo...@telavox.se <jo...@telavox.se> #249
wi...@risecalendar.com <wi...@risecalendar.com> #250
da...@montsecure.com <da...@montsecure.com> #251
ts...@degreed.com <ts...@degreed.com> #252
ja...@goodtime.io <ja...@goodtime.io> #253
mi...@vimcal.com <mi...@vimcal.com> #254
di...@harness.io <di...@harness.io> #255
ai...@completumhealth.com <ai...@completumhealth.com> #256
jo...@eox.at <jo...@eox.at> #257
br...@linearb.io <br...@linearb.io> #258
in...@rphants.com <in...@rphants.com> #259
we...@gmail.com <we...@gmail.com> #260
-1000 Aura
Description
I would like to be able to retrieve the Working Hours set by a user.
What is the purpose of this new feature?
The ability to retrieve this data will enhance the services that can be performed upon calendar data.
What existing APIs would this affect?
Google Calendar - Settings
What existing data does this use?
The user's settings data