Changes for page User Mentions

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -117,6 +117,7 @@
117	117	|UC8|UC7.1|[[Answering to a notification from the notification>>||anchor="HUC8.Answeringtoanotificationfromthenotification"]]|Medium|Low
118	118	|UC9|UC7.1|[[Answer to a notification by email>>||anchor="HUC9.Answertoanotificationbyemail"]]|Hard|Low
119	119	|UC10| | |TBD|Medium
	120	+|UC11|UC7.1| |Medium|Low
120	120
121	121	== UC1. Rich editor integration ==
122	122
...	...	@@ -167,18 +167,23 @@
167	167
168	168	TBD
169	169
170		-== UC6. Mentions history ==
	171	+== UC6. New mentions identification ==
171	171
172		-A user must not be notified of a mention several times for the same entity (document, comment, annotation...).
	173	+--A user must not be notified of a mention several times for the same entity (document, comment, annotation...).--
173	173
174		-A mapping between mentioned users (members of a group must be resolved to their individual users) and entities must be stored and used to identify the relevant notifications.
	175	+--A mapping between mentioned users (members of a group must be resolved to their individual users) and entities must be stored and used to identify the relevant notifications.--
175	175
176		-Similarly, only members present in a group prior to the group mentions should be notified.
	177	+--Similarly, only members present in a group prior to the group mentions should be notified.--
177	177
178		-A mapping between mentioned groups and entities must also be stored.
	179	+--A mapping between mentioned groups and entities must also be stored.--
179	179
180		-A notification is only sent to individual users that have not already be notified, and to groups that have not already been notified. Only group members who have not already been notified are notified.
	181	+--A notification is only sent to individual users that have not already be notified, and to groups that have not already been notified. Only group members who have not already been notified are notified.--
181	181
	183	+
	184	+A user must only be notified on the first save after the introduction of a mention.
	185	+
	186	+See the
	187	+
182	182	== UC7. Notifications ==
183	183
184	184	=== UC7.1 Notifications integration ===
...	...	@@ -197,6 +197,14 @@
197	197
198	198	When a mention links to an entity to which a user can answer (e.g., mentions and notifications), the mention must include a textarea allowing to quickly answer to the mention.
199	199
	206	+The way the answer is integration depends of the place where the mention originates from.
	207	+
	208	+|=Origin|=Answer
	209	+|Document body|The answer is integrated as an annotation around the user's mention in the document.
	210	+|Comment|The answer is integrated as a comment answering the originating comment.
	211	+|Annotation|The answer is integrated as a comment answering the originating annotation (which are actually handled as comment, so the UX is similar to the comment case).
	212	+|AWM textarea|As of today no mechanism allow a text to be attached on a specific text. Consequently, answering an AWM textarea is not supported and no answer should be proposed to the mentioned user in this case.
	213	+
200	200	== UC9. Answer to a notification by email ==
201	201
202	202	When a notification from a mention which a user can answer (e.g., mentions and notifications) is received by email, it should be possible to answer the email directly.
...	...	@@ -203,6 +203,8 @@
203	203
204	204	The answer is then integrated as an answer in the web interface.
205	205
	220	+Answering by email follows the same logic as UC8. Answering to a notification from the specifications.
	221	+
206	206	== UC10. Integration of browser notifications ==
207	207
208	208	Notifications can currently be displayed to the user through the notification menu and by email.
...	...	@@ -213,7 +213,14 @@
213	213
214	214	[[image:Screenshot from 2020-05-11 11-00-39.png]]
215	215
	232	+This feature is orthogonal to the integration of the user mentions, but allow a better integration of the user's notifications in her browser (and eventually in the underlying OS).
216	216
	234	+== UC11. Integration of answers from external source ==
	235	+
	236	+If the mentions is notified to an external user using an extension mechanism (for instance in the context of an integration of the user mentions with ActivityPub), answers to the notification (for instance by a comment on Mastodon), should be gracefully integrated in the UI.
	237	+
	238	+In summary, answering to mentions should be open to extensions.
	239	+
217	217	== Tasks on Jira ==
218	218
219	219	{{jira url="https://jira.xwiki.org" source="jql"}}
...	...	@@ -220,8 +220,14 @@
220	220	labels = mentions ORDER BY priority DESC
221	221	{{/jira}}
222	222
223		-== ==
	246	+= Implementation =
224	224
	248	+This section details further the implementation details of the user mention integration.
	249	+
	250	+== General guidelines ==
	251	+
	252	+The business logic triggered by introduction of a mention must be asynchronous and must not impact the reactiveness of  the UX.
	253	+
225	225	= Existing discussions =
226	226
227	227	This section collects discussions that are related to user mentions.