You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the new deployment, there are issues reported about incomplete contributor list for tagging in task comments section.
Another different issue I recognized recently: the wrong users seem to be listed when you put the "@" in the comment field in the tasking manager.
My most recent example is task 1109 of project https://tasks.hotosm.org/projects/15602 - the same was observed in task 1235 and 897 (here I indeed directed my comment to the wrong person...).
Back to task 1109: This task was marked as completely mapped by user Cameon (screenshot 1). While typing the @ sign users "Dlankler", "Miss Pooler", and "laurenko" are shown (see screenshot 2), but not e.g. user Cameon and PeterMN to whom I wanted to direct my thanks. It seems that the suggestions have nothing to do with the persons participating in the task ...
Did someone else recognize this behaviour in another project?
After the new deployment, there are issues reported about incomplete contributor list for tagging in task comments section.
Another different issue I recognized recently: the wrong users seem to be listed when you put the "@" in the comment field in the tasking manager.
My most recent example is task 1109 of project https://tasks.hotosm.org/projects/15602 - the same was observed in task 1235 and 897 (here I indeed directed my comment to the wrong person...).
Back to task 1109: This task was marked as completely mapped by user Cameon (screenshot 1). While typing the @ sign users "Dlankler", "Miss Pooler", and "laurenko" are shown (see screenshot 2), but not e.g. user Cameon and PeterMN to whom I wanted to direct my thanks. It seems that the suggestions have nothing to do with the persons participating in the task ...
Did someone else recognize this behaviour in another project?
cc @kaditya97 @royallsilwallz @konishon
The text was updated successfully, but these errors were encountered: