-
Notifications
You must be signed in to change notification settings - Fork 24
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
Add RT Summary Feature to IRCBot #226
base: master
Are you sure you want to change the base?
Conversation
|
||
|
||
def show_tickets(bot, date): | ||
"""Show RT tickets that need responses.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about this a bit, and I think the heuristic for "needs responses most" are the oldest tickets in a queue.
If someone submits a ticket today, its usually ok if we take a day to respond, but if its been a week we really should respond ASAP.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that is a much better idea!
ircbot/plugin/rt_summary.py
Outdated
from ocflib.infra.rt import RtTicket | ||
|
||
NUM_ITER = 10 | ||
NUM_LIST = 10500 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I see why this is 10500, but it probably deserves a comment above it on why it is 10500 (that's a recentish starting point to start searching from)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, hopefully we can figure out how to use the REST feature to find the most recent ticket instead. for now this should work!
Worked on with lmathias during hack day. Definitely want to figure out how to efficiently get the rt number for the latest ticket so we don't waste time finding it. I wanted to merge this pr to do a preliminary test in the #service-comm channel.