You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
benjagm opened this issue
Aug 26, 2024
· 0 comments
Labels
✨ EnhancementIndicates that the issue suggests an improvement or new feature.Status: AvailableNo one has claimed responsibility for resolving this issue.
Currently we are manually cancelling the Open Community Working Meetings 10 minutes before the start if there is no agenda or comments.
It will be great if we have a workflow checking the agenda 10 minutes before the meeting and if there is no agenda cancel it as not planned adding the closing comment:
"The meeting as been cancelled as there is no agenda for today. Thanks"
The next step is notify the cancellation sending a message to Slack through webhooks like we do in other workflows.
This will save tons of time to the Community Team.
The text was updated successfully, but these errors were encountered:
benjagm
added
✨ Enhancement
Indicates that the issue suggests an improvement or new feature.
Status: Triage
This is the initial status for an issue that requires triage.
Status: Available
No one has claimed responsibility for resolving this issue.
and removed
Status: Triage
This is the initial status for an issue that requires triage.
labels
Aug 26, 2024
✨ EnhancementIndicates that the issue suggests an improvement or new feature.Status: AvailableNo one has claimed responsibility for resolving this issue.
Description
Currently we are manually cancelling the Open Community Working Meetings 10 minutes before the start if there is no agenda or comments.
It will be great if we have a workflow checking the agenda 10 minutes before the meeting and if there is no agenda cancel it as not planned adding the closing comment:
"The meeting as been cancelled as there is no agenda for today. Thanks"
The next step is notify the cancellation sending a message to Slack through webhooks like we do in other workflows.
This will save tons of time to the Community Team.
The text was updated successfully, but these errors were encountered: