Skip to content
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

Remind TiCs to add post-event notes #550

Open
NoRePercussions opened this issue Jun 7, 2024 · 4 comments
Open

Remind TiCs to add post-event notes #550

NoRePercussions opened this issue Jun 7, 2024 · 4 comments
Assignees
Labels

Comments

@NoRePercussions
Copy link
Contributor

Tech currently has a policy that TiCs should add billing-related notes to the comments of each event. However, this is often forgotten after an event.

Tracker should send an email some time after an event completes that reminds TiCs to do so, potentially conditional on whether they've commented since the event ended.

Wellington also noted that we could send Slack notifications. It looks like Tracker is a bot, so we could roughly associate Tracker users and Slack users by email/phone. I'm not sure if that should be broken out into another issue.

@wjiang42
Copy link
Contributor

wjiang42 commented Jun 7, 2024

The bit about Slack notifications was @maxjkwang's lol

I think a good reminder time would be 24 hours after strike begins, since all relevant ends should have a strike time, and few events have strikes longer than a day. Damn Perry's idea is so much better

@DaAwesomeP
Copy link
Member

This can probably build off of the already implemented feature that marks events as completed to schedule the job.

There should be an event checkbox (checked by default) to enable this. We should pick some nice time to notify on the following day (9am?) in case strike ends at midnight.

This one definitely requires #544.

@DaAwesomeP
Copy link
Member

For Slack DMing, yes maybe a separate issue to make a method to send a notification to one or more people. I believe we can lookup users by email. Rob has played around with this and we can ask him in a separate thread.

@maxjkwang
Copy link

Yeah my initial thoughts were to notify the following noon, but I guess 9am is also fine, not a big problem.

If it's easy to implement then that's nice.

@NoRePercussions NoRePercussions self-assigned this Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants