In T141287#2565426, @greg wrote:One easy thing to do would be to ping all of the very old tasks (eg: tasks who's last update was me adding them to #wikimedia-incident on July 27+28th) with a note like:
"This task is a follow-up action from an incident report and has not recently seen updates. If this is no longer a valid task/actionable or it has been superseded by another one, please indicate as such. If it is still valid you should prioritize this work appropriately in your team/personal backlog. If you have any questions feel free to ask me (Greg Grossmeier)."
(wordsmithing appreciated if this idea makes sense)
It might make sense to rerun that query at the end of this quarter so that there is more than 20 days from when I added Wikimedia-Incident (there'd be ~60 days). NB: When I went through and added Wikimedia-Incident to those tasks I only made it as far back as May 2016 see: T141493#2500584. It's tedious.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | greg | T144973 Ping tasks in #wikimedia-incident without recent activity for follow-up near the end of FY1617Q1 | |||
| Resolved | greg | T141287 Plan how to improve reminders for teams/people to address identified actionables from incident reports |
Event Timeline
Comment Actions
Updated wording (thanks Kevin):
"This follow-up task from an incident report has not been updated recently. If it is no longer valid, please add a comment explaining why. If it is still valid, please prioritize it appropriately relative to your other work. If you have any questions, feel free to ask me (Greg Grossmeier)."