#993: Quire Feedback
Status: Completed
Problem
We have some code which uses @ symbol, which is defined in the quire as a "mention" tag. Means @someone.
We found out that we mention many people because of that, which is very insecure, bad, and weird.
Suggestion: Add an option to organization / or settings which are block mentioning different people, and not convert the @something to a human which does not belong to the project.
Again, the main purpose of the suggestion is dropping @ tag for calling people which is not a part of the project/organization.
How feature must look in result
- I enter @something bla bla bla
- This, for example, @something it's a real user in quire. By default, that means we are mentioning him, and he will receive notifications (as far as I understand) and maybe access to the task to read it.
- This @something user will not be mentioned if we have an option in our settings, and will not be converted as a link to the user which exists in the quire.
- The @something will not receive any notifications and so on.
- Overall performance in your own app because of restricting such access to all users in quire will be heavily increased. Because not need every time to parse tons of users via @tag
Created by DrWho May 26, 2018, Edited Feb 24, 2021
Hi DrWho, What we would suggest is use “code block”. For example:
will turn into:
Crystal, May 29, 2018