I didn't know inline comments didn't submit on their own, there isn't any visual indication like on Differential. Personally, I think the use case here is different than in Differential and that a full comment submit shouldn't be needed, they should just post/save. I would also argue that maybe Differential should do the same, which solves race-condition peer reviews, but we can discuss that another time.
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Restricted Maniphest Task | ||||
Resolved | epriestley | T1315 Phacility Launch Status | ||
Resolved | epriestley | T2795 Phacility (Mid Priority) | ||
Resolved | chad | T2637 Unbeta Pholio | ||
Resolved | chad | T2636 It's difficult to know an inline comment didn't post/save in Pholio | ||
Restricted Maniphest Task |
Event Timeline
The big reason we batch them is: if I leave 30 inlines, should we send 30 emails?
(Less concretely: my inlines often don't make sense without the context of the main comment [and I believe this is common in general]; I often revise inlines heavily during review.)
We should definitely indicate the draft state prominently, though.
You raise a good point for Differential. I don't know if it is perfectly parallel in Pholio. What about some way of letting the user decide if they want to add additional info or just leave an inline comment in Pholio? The problem I'm seeing is with comments living on the mocks as well as inline leads to this disjointed timeline of partial conversations. It just seems more of an issue to me in Pholio vs. Differential. It also might be how the transactions are rending in the Timeline. Inline comments render as individual transactions instead of inside a comment.
If we just want to punt and stick to what Differential does, this task is essentially:
- Show a draft state to an inline comment.
- Have inline comment appear inside other comment transaction.
Is that correct?
I would love to 'tag' this with a status of 'launch blocker' or something to let us know to fix it before un-beta. :)