microsoft / microsoft/work-iq

Feature Request: Surface attendee response status (accepted/declined) for calendar events

Open
#50 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

gap
Dominant language
PowerShell
Stars
1k
Forks
132
Avg merge
5d 19h
Merged PRs (30d)
6

Description

Summary

When querying calendar events via workiq ask, the response includes meeting details (title, time, organizer, attendees) but does not surface the attendee responseStatus field. This makes it impossible to determine whether an attendee has accepted, declined, or not responded to a meeting.

Use Case

I run a daily briefing that checks my calendar for 1:1 meetings. If the other person has declined, I want to know so I can skip the meeting. Currently I have to open Outlook and check the tracking tab manually for each 1:1.

What Happens Today

workiq ask -q "For any meetings today with '1:1' in the title, have any attendees declined?"

WorkIQ returns the meeting title and attendee names, but reports that attendee RSVP status is "not available" in the meeting data. The response confirms that the search surface does not expose the responseStatus field.

Expected Behavior

The calendar query response should include each attendee's response status. The data is available in Microsoft Graph on the event object at attendees[].status.response, which returns one of: accepted, declined, tentativelyAccepted, or none.

Additional Context

  • WorkIQ version: 0.2.8.13483
  • The calendar events themselves are returned successfully, so WorkIQ already has access to the event data. The responseStatus field just needs to be included in what gets surfaced.
  • Tested with both direct calendar queries and email searches for decline notifications. Neither approach surfaces this information.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the workiq ask calendar-query entry point and trace how Microsoft Graph event attendees are represented; inspect attendees[].status.response as the expected source. Done means calendar responses expose accepted, declined, tentativelyAccepted, or none for each attendee while retaining the existing event details.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.