Page MenuHomePhabricator

Improve "unblock task" feed stories
ClosedPublic

Authored by epriestley on Aug 12 2014, 4:22 PM.
Tags
None
Referenced Files
F19310794: D10235.id24626.diff
Wed, Dec 24, 10:32 PM
F19081411: D10235.diff
Dec 2 2025, 6:30 AM
F19081409: D10235.diff
Dec 2 2025, 6:27 AM
F18844042: D10235.id24627.diff
Oct 29 2025, 2:46 AM
F18844040: D10235.id24626.diff
Oct 29 2025, 2:46 AM
F18844039: D10235.id24628.diff
Oct 29 2025, 2:45 AM
F18777445: D10235.diff
Oct 11 2025, 3:01 AM
F18712081: D10235.id.diff
Sep 29 2025, 5:16 AM
Subscribers

Details

Summary

Fixes T5184. Fixes T5008. Three issues with stories/notifications about changing the status of tasks which block other tasks:

Bad Feed Stories

  • Problem: Feed story rendering was confusing (T5184).
  • Solution: fix it to provide context.

Too Many Feed Stories

  • Problem: Feed gets a story for the original task's close ("a closed x"), and a story for each blocked task ("a closed x, a task blocking y").
  • "Solution": Punt. These are redundant in the full feed but not in filtered feeds. Right solution is display-time aggregation. No users have really complained about this.

Too Many Notifications

  • Problem: Users subscribed to both tasks get notified about the clsoe, and also about the unblocked task. These notifications are redundant.
  • "Solution": Punt. This is easy to fix by silencing notifications for the sub-editor, but I'm worried it would be confusing. Users haven't complained. Display-time aggregation might be a better fix.
Test Plan

Screen_Shot_2014-08-12_at_9.22.20_AM.png (95×612 px, 15 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Skipped
Unit
Tests Skipped