Page MenuHomePhabricator

Select all available bodies when rendering a feed story
ClosedPublic

Authored by epriestley on Nov 5 2013, 4:40 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Sep 4, 7:04 PM
Unknown Object (File)
Sun, Sep 1, 4:04 AM
Unknown Object (File)
Sun, Aug 25, 10:12 PM
Unknown Object (File)
Sun, Aug 25, 5:56 PM
Unknown Object (File)
Sun, Aug 25, 8:20 AM
Unknown Object (File)
Tue, Aug 20, 7:36 AM
Unknown Object (File)
Aug 3 2024, 7:06 AM
Unknown Object (File)
Jul 26 2024, 11:10 AM
Subscribers
Tokens
"Doubloon" token, awarded by btrahan.

Details

Summary

Fixes T4060. The logic here is:

  • When you take several actions at once, we show a single feed story for all of them.
  • We choose the "most interesting" title for the feed story. For example, "close task" is more interesting than "add CC".

Currently, the issue with this is:

  • "Add comment" is the least interesting title. I think this is correct: all other actions are more interesting than the fact that you added a comment.
  • We try to conserve the number of objects we need to load by rendering only the most interesting transaction.

To fix this:

  • Stop being so conservative; load all of the transactions and all of their PHIDs.
  • Add bodies from any transactions which render bodies. In all cases (I think?) this is a maximum of one comment adding a body.

The end result is a story like this:

epriestley closed T123: the building is on fire.

"Okay guys I put the fire out"
Test Plan

See screenshot.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Add comment being higher than updated subscribers seems more correct though (but, yes, below everything else).

Maybe the rule should be something like this:

  • If you add only yourself as a subscriber only, the CC transaction has low strength (say, 0.25).
  • If you add anyone else or remove yourself, the CC transaction has normal strength (1.0).
  • "Comment" currently has strength 0.5.

...since adding CCs other than yourself seems very slightly more interesting than "commented"?

The "updated" text is also lazy, it should eventually show the full action ("epriestley added alincoln as a subscriber.").

Yeah, that seems like the "best" rendering for consistency and user-expectation, once the text shows names it could probably go either way :) (though just "Added Comment" for the trivial case still seems marginally better for UX).

Yeah, that makes sense to me. That wouldn't apply to Maniphest for now anyway since it still has funky custom subscription management, but I'll probably add that rule when I clean up the strings, probably after switching Maniphest over.