Feature-request: add sleep data to the sdk (2022)

Our goal as QA is to look into and bring all reported issues to development so they can make a determination on it. This particular issue was approved by development to be worked on, but has yet to be implemented.

Our goal as QA is to look into and bring all reported issues to development so they can make a determination on it. This particular issue was approved by development to be worked on, but has yet to be implemented.

Temperature is rising since Mar 8, 2022

Is it just me or is it getting hot in here

Thank you for coming back to us after weeks of silence. The news you are bringing is not showing you guys in the good light (especially that lost data during the workflow transferring issue), however let us put the past behind.

Now what we need to know is:
- Do you have it analyzed yet, estimated and ready for development - if yes - WHEN it is planned to be developed? Next sprint? Next iteration? Q2 or Q3 of 2025?

Look how many people expect you guys to take action - we really need status, timeline and results from the Garmin product development team.  

It's good to know that this issue has at least been "approved by development to be worked on" even if it hasn't been implemented yet. However, if this is indeed the case, I'm not sure why you have suggested creating a new ticket if we think it is still an issue. It hasn't been implemented yet, so it obviously is still an issue for those that care about it enough to visit this form. But if it's been approved for development and just hasn't been implemented yet, wouldn't opening a new ticket be redundant?

Your comments have left me confused as to what the actual status of the request is. Not yet seen by anybody that matters? Under consideration? Declined? Actively under development? Already implemented? Some clarification would be fantastic.

Then please pick this one, place it on the backlog and let the product manager put it onto the release train. Only then we will see it implemented soon.