We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
keyword_webex resolution_fixed type_enhancement | by pusateri@bangj.com
keyword_webex
resolution_fixed
type_enhancement
Some sessions now contain remote_instructions for joining a webex conference. As an example, see: https://datatracker.ietf.org/api/v1/meeting/session/28002/
It would be useful to have this information in the sessions returned by the alternate JSON API which is requested as: https://datatracker.ietf.org/meeting/interim-2020-lsr-02/agenda.json
Issue migrated from trac:2955 at 2022-03-04 07:48:08 +0000
The text was updated successfully, but these errors were encountered:
@rjsparks@nostrum.com changed status from new to accepted
new
accepted
Sorry, something went wrong.
@pusateri@bangj.com changed status from accepted to closed
closed
@pusateri@bangj.com changed resolution from `` to fixed
fixed
@pusateri@bangj.com commented
Fixed in d275a78:
Add agenda_note and remote_instructions to agenda.json API. Commit ready for merge. Fixes #2955.
@henrik@levkowetz.com commented
Fixed in f53d03e:
Merged in d275a78 from pusateri@bangj.com: Add agenda_note and remote_instructions to agenda.json API. Fixes #2955.
No branches or pull requests
keyword_webex
resolution_fixed
type_enhancement
| by pusateri@bangj.comSome sessions now contain remote_instructions for joining a webex conference. As an example, see:
https://datatracker.ietf.org/api/v1/meeting/session/28002/
It would be useful to have this information in the sessions returned by the alternate JSON API which is requested as:
https://datatracker.ietf.org/meeting/interim-2020-lsr-02/agenda.json
Issue migrated from trac:2955 at 2022-03-04 07:48:08 +0000
The text was updated successfully, but these errors were encountered: