Skip to content
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

Starting and stopping the Drive activity notifications even if they are already started or stopped should show correct error. #3

Open
AayushChaudhary0001 opened this issue Jul 11, 2024 · 1 comment
Assignees

Comments

@AayushChaudhary0001
Copy link

AayushChaudhary0001 commented Jul 11, 2024

This issue was found during the testing of this plugin.

For start activity slash command:
If the user runs the slash command "/drive notifications start" even if the notifications were already started (enabled), the user receives the message that the notifications have been started, instead, it should be that they are already enabled. This is a suggestion if we can work on it.

For stop activity slash command:
If the user runs the slash command "/drive notifications stop" even if the notifications were already stopped (disabled), the user should receive a message that they are already stopped, or there should be a consistency with the case above. But the user receives a message of something went wrong and contact your org admin.

@darkLord19
Copy link
Contributor

@AayushChaudhary0001 this is fixed on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants