Page MenuHomePhabricator

Combine Flow resolved and summarised events when they are part of the "mark as resolved" workflow
Open, Needs TriagePublic

Description

When users resolve a topic in flow, they are encouraged to provide a closing summary. While this involves two technical steps (marking as resolved and summarisation) the user may perceive it as part of the resolution process.

mark-resolved-anim.gif (161×328 px, 51 KB)

The resolution workflow usually generates two separate notifications (resolved, and summarised), where a single one would be preferred: the topic was resolved (and the final summary is included as an excerpt).

The proposed behaviour in the different cases is:

  • The user resolves a topic and provides no summary: a "topic was resolved" notification is sent.
  • The user resolves a topic and provides a summary as part of the resolution process: a "topic was resolved" notification is sent which includes an excerpt of the summary (note that a separate summary edited notification is not sent).
  • The user edits the summary of a notification out of the process of marking it as resolved: an edited summary" notification is sent.

This not only reduces the number of notifications but helps to convey for the summary the meaning of "final outcome" for the resolution.

This idea was previously discussed in T125119: Should get notified for topic summary change on your own user talk and T125654: Notify when a topic is marked as resolved or reopened

Event Timeline

Both refer to the same idea. An aspect missing on the original T125654 ticket which was not implemented and it seems that both @Trizek-WMF and me decided to capture in a separate ticket to make sure it didn't get lost.
Feel free to merge them in the direction that makes more sense.