-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
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
Coordinate texters' schedules/availability and commitments (target counts) to campaigns #218
Comments
Does dynamic assign serve this purpose? Or were you thinking of something else? @schuyler1d |
Somewhat. I think politics rewired branch and others have done some integration directly with slack channels. This and another old ticket makes me wonder whether we should have some abstraction like an "assignment-loader" 🙃 |
We have the concept of an Assignment Request, which has a target (team and initials vs replies) and a desired amount. Texters can submit an Assignment Request from the Texter to-do list page. Assignment Requests can then be managed from a page on the admin side. We support 3rd party management of Assignment Requests with webhooks. You can configure an external webhook to hit when an assignment request is created. That service can then respond by hitting a protected Spoke endpoint to either approve or deny the request. |
An assignment-loader would fit into that sort of framework ^ allowing for webhook integrations |
Just trying to wrap my head around the title and description + comments in this issue. Is it now a feature request for an "Assignment-loader" that could then be the backend for a Request Texts UI for texters and an Assign Texts UI for admins? |
Closing because this is addressed with #1533 |
Currently, texters are assigned top-down in the interface a certain number of targets. Often through a side-channel, texters communicate how many they want and when they are available -- e.g. by signing up for shifts.
Can Spoke coordinate between RSVPs/signups from a schedule/calendar?
The text was updated successfully, but these errors were encountered: