feat: improve user assignments via quick add magic #3348
|
@ -76,10 +76,8 @@
|
|||
"savedSuccess": "The settings were successfully updated.",
|
||||
"emailReminders": "Send me reminders for tasks via Email",
|
||||
"overdueReminders": "Send me a summary of my undone overdue tasks every day",
|
||||
"discoverableByName": "Let other users find me when they search for my name",
|
||||
"stillDiscoverableByName": "Users can still find you by name if they want to assign you to a task on a project shared with you.",
|
||||
"discoverableByEmail": "Let other users find me when they search for my full email",
|
||||
"stillDiscoverableByEmail": "Users can still find you by email if they want to assign you to a task on a project shared with you.",
|
||||
"discoverableByName": "Allow other users to add me to teams or projects when they search for my name",
|
||||
"discoverableByEmail": "Allow other users to add me to teams or projects when they search for my full email",
|
||||
"playSoundWhenDone": "Play a sound when marking tasks as done",
|
||||
"weekStart": "Week starts on",
|
||||
"weekStartSunday": "Sunday",
|
||||
|
|
|
@ -48,18 +48,12 @@
|
|||
<input type="checkbox" v-model="settings.discoverableByName"/>
|
||||
{{ $t('user.settings.general.discoverableByName') }}
|
||||
</label>
|
||||
dpschen marked this conversation as resolved
|
||||
<p class="is-size-7" v-if="!settings.discoverableByName">
|
||||
{{ $t('user.settings.general.stillDiscoverableByName') }}
|
||||
</p>
|
||||
</div>
|
||||
<div class="field">
|
||||
<label class="checkbox">
|
||||
<input type="checkbox" v-model="settings.discoverableByEmail"/>
|
||||
{{ $t('user.settings.general.discoverableByEmail') }}
|
||||
</label>
|
||||
<p class="is-size-7" v-if="!settings.discoverableByEmail">
|
||||
{{ $t('user.settings.general.stillDiscoverableByEmail') }}
|
||||
</p>
|
||||
</div>
|
||||
<div class="field">
|
||||
<label class="checkbox">
|
||||
|
|
Reference in New Issue
Block a user
By
discoverable
you mean "able to invite"?Because I can't assign someone if that person isn't part of the current project, correct?
In general I was now quite confused what this setting now actually does. Judging from this most users will probably not have a clue.
That's correct! Before the recent changes about finding users in the api, this setting would apply to searching users with access to a project as well. Now it does not anymore and the little explanation I added below does not make this clearer. I've adjusted the message and removed the explanation below the setting.
No, it's literally adding a user to a project or team. Mentioning is a topic for another day.
Inviting implies there's a form of "receiving an invitation and be able to reject it" which is not the case right now. There is an item on the roadmap to change that, but that's very much out of scope here (and it requires quite a few changes in the api).
We absolutely should group these settings more. Right now there's too much stuff and it does not look great. I'd prefer to move that to another PR since it would touch more than these two options and I feel like we should plan this properly first.
I guess that depends on how common your name is :) I think it makes sense to have them as distinct options, because an email address is unique, but a name might not be. Searching for a name also "feels" more personal than allowing someone else to find me by my email address.
How about 'add member' then?
makes sense
keep splitting options
Makes sense as well
I've changed the string yet again