-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tell editors before sending task requests to unactivated email addresses #2822
Labels
new feature
A new thing that doesn't exist yet
Comments
This is a good short term alternative 👍
…Sent from my iPhone
On 1 Apr 2022, at 12:44, Joseph Muller ***@***.***> wrote:
Is your feature request related to a problem? Please describe.
We often get support requests for situations in which an editor has sent a task to someone who has had trouble accessing that task in Janeway. Often this happens when the person has duplicate accounts: the task was sent to one account, but the user is logging in with the other account. Often, the account the user is not logging into is inactive.
Describe the solution you'd like
To facilitate better communication about what email address to use, we could check whether an account is active before Janeway creates a task and ask the task creator to confirm the action. This may head off many of these situations because it will let them know that the task will be created for an account the user does not (yet) have access to.
Describe alternatives you've considered
We could use individualised task links that allow Janeway to figure out whether the person has logged into the correct account for a given task. This would be a larger feature for down the road.
—
Reply to this email directly, view it on GitHub<#2822>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB7PSYTLOGA53GEDNBEJI6LVC3OR3ANCNFSM5SIOARLA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
joemull
added a commit
that referenced
this issue
Aug 1, 2022
joemull
added a commit
that referenced
this issue
Aug 1, 2022
joemull
added a commit
that referenced
this issue
Aug 1, 2022
joemull
added a commit
that referenced
this issue
Aug 2, 2022
joemull
added a commit
that referenced
this issue
Aug 2, 2022
joemull
added a commit
that referenced
this issue
Aug 2, 2022
joemull
added a commit
that referenced
this issue
Aug 2, 2022
joemull
added a commit
that referenced
this issue
Aug 2, 2022
joemull
added a commit
that referenced
this issue
Aug 2, 2022
joemull
added a commit
that referenced
this issue
Aug 2, 2022
joemull
added a commit
that referenced
this issue
Aug 2, 2022
joemull
added a commit
that referenced
this issue
Aug 2, 2022
joemull
added a commit
to openlibhums/typesetting
that referenced
this issue
Aug 3, 2022
…reader accounts
joemull
added a commit
that referenced
this issue
Aug 3, 2022
ajrbyers
added a commit
that referenced
this issue
Aug 18, 2022
ajrbyers
pushed a commit
to openlibhums/typesetting
that referenced
this issue
Sep 7, 2022
…reader accounts
joemull
added a commit
that referenced
this issue
Sep 8, 2022
joemull
added a commit
that referenced
this issue
Sep 8, 2022
joemull
added a commit
that referenced
this issue
Sep 8, 2022
joemull
added a commit
that referenced
this issue
Sep 8, 2022
joemull
added a commit
that referenced
this issue
Sep 8, 2022
joemull
added a commit
that referenced
this issue
Sep 8, 2022
joemull
added a commit
that referenced
this issue
Sep 8, 2022
joemull
added a commit
that referenced
this issue
Sep 8, 2022
joemull
pushed a commit
that referenced
this issue
Sep 8, 2022
Repository owner
moved this from PR Submitted
to Done
in v1.4.3
Sep 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
We often get support requests for situations in which an editor has sent a task to someone who has had trouble accessing that task in Janeway. Often this happens when the person has duplicate accounts: the task was sent to one account, but the user is logging in with the other account. Often, the account the user is not logging into is inactive.
Describe the solution you'd like
To facilitate better communication about what email address to use, we could check whether an account is active before Janeway creates a task and ask the task creator to confirm the action. This may head off many of these situations because it will let them know that the task will be created for an account the user does not (yet) have access to.
Describe alternatives you've considered
We could use individualised task links that allow Janeway to figure out whether the person has logged into the correct account for a given task. This would be a larger feature for down the road.
The text was updated successfully, but these errors were encountered: