License: Apache License 2.0

Makefile 8.67% Go 84.63% JavaScript 3.86% TypeScript 2.84%

mattermost-plugin-google-drive's Introduction

Mattermost Google Drive Plugin

Help Wanted Tickets here

Overview
Features
Admin Guide
End User Guide
Contribute
Security Vulnerability Disclosure
Get Help

Overview

This plugin allows you to integrate Google Drive to your Mattermost instance, letting you:

Create a Google Drive file
Share a Google Drive file
View and reply to comments
Upload any file attached to a Mattermost post directly to your Drive
Enable or disable notifications for comments and files permission changes

Admin Guide

End User Guide

Get Started

Use the Plugin

Slash commands

After your System Admin has configured the Google Drive plugin, run /drive connect in a Mattermost channel to connect your Mattermost and Google accounts.

Connect to your Google account


`/drive connect`	Connect your Mattermost account to Google.
`/drive disconnect`	Disconnect your Mattermost account from Google.

Create Google Drive files


`/drive create doc`	Create and share a new google document.
`/drive create sheet`	Create and share a new google spreadsheet.
`/drive create slide`	Create and share a new google presentation.

Subscribe yourself to notifications


`/drive notifications start`	Enable Google Drive activity notifications.
`/drive notifications stop`	Disable Google Drive activity notifications.

Post menu bindings

Upload file to Google drive:: This option is available in any post to upload any attached files directly to your google drive. You will be prompted with a dropdown to choose the attachment you want to upload. Upload all files to Google drive:: This option is available in any post to upload all the attached files directly to your google drive. You will be prompted with a confirmation to upload all the attached files.

How do I share feedback on this plugin?

Wanting to share feedback on this plugin?

Feel free to create a GitHub Issue or join the Google Drive Plugin channel on the Mattermost Community server to discuss.

Contribute

I saw a bug, I have a feature request or a suggestion

Please fill a GitHub issue, it will be very useful!

Development

Pull Requests are welcome! You can contact us on the Mattermost Community ~Plugin: GoogleDrive.

This plugin contains server and webapp both portions. Read our documentation about the Developer Workflow and Developer Setup for more information about developing and extending plugins.

To avoid having to manually install your plugin, build and deploy your plugin using one of the following options.

Deploy with local mode

If your Mattermost server is running locally, you can enable local mode to streamline deploying your plugin. After configuring it, just run:

Security vulnerability disclosure

Please report any security vulnerability to https://mattermost.com/security-vulnerability-report/.

Get Help

For questions, suggestions, and help, visit the Google Drive Plugin channel on our Community server.

mattermost-plugin-google-drive's People

Contributors

Stargazers

Watchers

Forkers

darklord19

mattermost-plugin-google-drive's Issues

Bulk option upload option visible for the post which contains only single attachement.

The option for uploading all the files to the drive is open for the post where only single attachment is present.

Steps to reproduce:-

Post a message which consist single attachment.
Open the action menu.
Click on upload all the files to drive.

Since the post contain single attachment, this option should not be visible(or can be disabled) in such case

Cancelling the file upload process to drive still shows success message

If a user tries to cancel the bulk upload of files to drive, he still receives the success message that the files have been uploaded.

Steps to reproduce:

Post any attachement in the channel.
Open the action menu.
Click on upload all files to drive
Click on the cancel button.

The process should have been stopped, instead the user receives the message of process successfully completed.

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

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.

Success and error message received from system bot instead of Google Drive bot

On uploading the files to drive from the action menu button, the success and error message are received from the system bot, instead of drive bot.

Steps to reproduce:

Post any attachement in the channel.
Open the action menu.
Click on upload the file to drive.

The success message or the error message will be received from the system bot which should have been received from the google drive bot.

unable to generate webapp bundle

unable to generate webapp bundle: com.darklord.plugin-google-drive: unable to copy webapp bundle directory: com.darklord.plugin-google-drive: stat /mattermost/plugins/com.darklord.plugin-google-drive/webapp/dist: no such file or directory

File type with permission anyone with the link can view, comment and edit are not working.

If a user creates a file with a permission type of anyone with the link can view/comment/edit the file and shares it in the channel, not every user is able to access the file with the link. It actually requires the access from the file owner to open that file. This issue is common for all permissions namely view, comment and edit with anyone with the link

Inconsistency in the readme file as compared to the slash command response.

An inconsistency has been noticed in the readme file.

On running the help slash command, the response of that command does not matches with that present in the readme file.
For example, the response of help slash command shows the events on which the notifications would be sent to the users for drive activity, whereas this is not mentioned in the readme file, which should be consistent everywhere.

Supported screenshots:-

Slash command response
Readme file

It might be possible that these 2 can not be exactly same, but they should consist similar information. If we take the example above, the events for which the notifications should be sent are not listed in readme file.

Running disconnect slash command even after the account is disconnected shows wrong error.

If the user is already disconnected and still runs the command "/drive disconnect", the user receives the error that the account is disconnected. Instead, the error should be that the account is already disconnected.

Created file type not getting shared in the channel

During testing of this plugin, I found a bug which is not consistent.

When a user runs the command to create a doc/slide/sheet, and checks the checkbox to share it to the channel as well, the file type is not always shared on the channel.

Steps to reproduce:-

Run the "/drive create < desired file type >" .
Fill the mandatory fields and check the channel sharing checkbox.
Open the channel where the file was shared.

The shared file is not getting reflected in the channel

Note:- This bug is not consistent, you might not be able to reproduce it every time.

Starting and stopping the notifications slash commands are not working

As a user, the notifications for commenting and sharing any file type in the drive are not working.